Temporal fix: Handle wrapped JSON-RPC responses in callServerTool #82
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.
Summary
This is a temporal workaround until host implementations properly unwrap JSON-RPC responses.
Some host implementations incorrectly return the full JSON-RPC envelope instead of just the unwrapped result from
callServerTool(). This causes apps to fail when accessingresult.content.Problem
Apps using
callServerTool()receive:{ "result": { "content": [...] }, "jsonrpc": "2.0", "id": 1 }But expect:
{ "content": [...] }Solution
Add a temporal hack in
callServerTool()to detect and unwrap the JSON-RPC envelope when present. This can be removed once host implementations are fixed.🤖 Generated with Claude Code