feat(mcp): enhance tool output handling and schema definitions #11464
+67
−12
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
- Added a new function `toModelOutputFromMcpCallToolResult` to standardize the output processing from MCP calls, supporting various output formats. - Updated `ToolSchemas` type to include optional `outputSchema` for better flexibility in tool definitions. - Modified the `tools` method in `DefaultMCPClient` to utilize the new output handling function and improved schema handling for tool execution. This update improves the robustness of tool output management and aligns with the evolving requirements of the MCP client.
Contributor
|
marking this as closed since this has been fixed via #11543 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Background
I need tighter MCP ↔ LLM integration so tool call results can be better consumed without overflowing the context window. This enables downstream behaviors like reading specific properties, filtering, and validating/parsing results based on a tool’s declared output shape.
Summary
tools/callresults into LLM-friendlyToolResultOutput:toolResultorstructuredContent), we return it as JSON model output so the LLM (and app code) can work directly with properties.isError), we return error text extracted from text content for better surfaced failures.contentarray.outputSchemaon MCP tool definitions and plumbed it through when building AI SDK tools, so consumers can parse/validate tool outputs using the declared schema.Manual Verification
outputSchemawhen present).isErroris set).Checklist
pnpm changesetin the project root)Future Work
outputSchemato parse results.Related Issues