fix: preserve custom results with generic metadata - #1197
Open
jmagar wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
ServerResultis an untagged union.CallToolResultcurrently accepts protocol-generic_metaas sufficient evidence that a response is a tool result. Custom MCP extension results that legitimately carryresultType: completeand_metacan therefore be consumed asCallToolResult, dropping extension-specific fields before callers can deserialize them.This change requires at least one tool-specific field (
content,structuredContent, orisError) beforeCallToolResultmatches. GenericresultType/_metaalone fall through toCustomResult.Regression coverage
resultType,_meta, andskillsremainsCustomResultcontentand_metaremainsCallToolResultFocused
rmcplibrary tests pass on current main (3.1.4).