{{ message }}
OutputSchema support in MCP tools - #654
Closed
bzsurbhi wants to merge 6 commits into
Closed
Conversation
bzsurbhi
marked this pull request as draft
May 13, 2025 22:16
bzsurbhi
marked this pull request as ready for review
May 23, 2025 00:16
bzsurbhi
changed the title
There was a problem hiding this comment.
Slightly confused didn't modelcontextprotocol/modelcontextprotocol#356 get paused awaiting more evidence extra complexity is worth while.
Author
There was a problem hiding this comment.
You're right. I updated the PR as per the new schema
|
Looks like I missed this merge request, I'm happy for maintainers to cherry pick from #685 the bits you want to keep, if you want any help in cherry picking let me know |
Contributor
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
4 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.
Add outputSchema support to MCP tools
Motivation and Context
Implemented changes in PR for outputSchema
Key implementation details:
outputSchemafield to theToolclass to store the JSON schema for tool outputsfunc_metadatato extract return type annotations and generate JSON schemasHow Has This Been Tested?
Added tests with tools using various return types including:
Breaking Changes
No breaking changes. The outputSchema is optional and backward compatible with existing tools.
Types of changes
Checklist
Additional context