Motivation and Context

I was comparing the specification (https://modelcontextprotocol.io/specification/draft/server/resources#resource-contents) against the schema reference (https://modelcontextprotocol.io/specification/draft/schema#resourcecontents) when I noticed that the spec shows the name and title properties to both TextResourceContents and BlobResourceContents. This hints that the base ResourceContents extends BaseMetadata but the schema reference is not showing this.

Specification:

Schema Reference:

How Has This Been Tested?

npm run check:schema:ts
npm run generate:schema
npm run serve:docs
npm run check:docs
npm run format

Breaking Changes

This does not break the spec but SDKs might need to update their types if they depend on the schema reference here.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context