A Resource has a uri and a name; a Resource Template has a uriTemplate and a name. Both accept only the properties of their Section 10 tables, each with its defined type.
Requirement
Section titled “Requirement”Resource and Resource Template Objects have their required fields, defined property types, and no unknown properties.
Details
Section titled “Details”Rule ID: mcpdesc.resource.members
Owner: mcpdesc
Surface: Resource, ResourceTemplate
Kind: structural
Requirement level: must
Protocol versions: independent of the MCP protocol version
Document schema locations: #/$defs/resource, #/$defs/resourceTemplate
Status: internal · Enforcement: internal
Required by
Section titled “Required by”- MCP Description 0.9.0, Sections 10.1.1 and 10.2.1
- 10. Resources and Resource Templates: req-resource-fields
-
- Resources and Resource Templates: req-resource-template-fields
-
- Tags: req-entity-tags-shape
-
- Tags: req-entity-tags-unique
Examples
Section titled “Examples”Invalid example
Section titled “Invalid example”Source: expected-invalid/malformed-info-transport-tag-resource.json · Selected: /resources/0
{ "name": "readme", "mimeType": "text/markdown"}Rule Source Code
Section titled “Rule Source Code”resource.yaml at immutable tag v0.9.0-rc.3.