Remove non-spec fields from resource content responses #110
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Text and Blob content classes were including name and title fields in their toResource() output, which are not part of the MCP specification for resource contents.
Changes
According to the https://modelcontextprotocol.io/specification/2025-06-18/schema#textresourcecontents:
TextResourceContents should only include:
BlobResourceContents should only include:
The name and title fields belong to the resource descriptor itself, not the content payload.