modelcontextprotocol / modelcontextprotocol/modelcontextprotocol
EmbeddedResource returns a single content block, ReadResourceResult returns an array
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.3k
- Forks
- 1.8k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 25
Description
Is your feature request related to a problem? Please describe.
EmbeddedResource delivers a content block and a uri, where the uri can be used to re-fetch later via resources/read. However, the result of the latter (a ReadResourceResult) delivers an array of content blocks.
Practical consequence is that EmbeddedResources can't embed the full content of multi-block resources.
Less practically, it's an inconsistency in the "EmbeddedResources are pre-fetched Resources, with a uri for re-fetching" high-level design.
Describe the solution you'd like
Modify EmbeddedResource to deliver an array of content blocks.
Describe alternatives you've considered
Leave it alone.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the protocol specification definitions for EmbeddedResource and ReadResourceResult, then compare how each represents content blocks. Check any related schema examples or generated types in the specification project. Done means the two resource representations are consistent and multi-block resources can be embedded without losing content.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100