feat: add MCP tool call result callback#3479
Open
seratch wants to merge 1 commit into
Open
Conversation
2 tasks
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
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.
This pull request adds a
tool_call_result_callbackoption for local MCP servers so applications can observe MCPCallToolResultmetadata without changing the model-visible tool output. The callback receives anMCPToolCallResultContextwith the original MCP tool name, public display name, parsed arguments,_meta,structuredContent,isError, and a copied tool output, which lets apps collect frontend-facing data for dual-output MCP tools while keeping replay and model history behavior unchanged.This pull request resolves #3477.