docs: fix Tool inputSchema example to produce valid JSON Schema#253
Closed
ZhouYinLong-lab wants to merge 1 commit into
Closed
docs: fix Tool inputSchema example to produce valid JSON Schema#253ZhouYinLong-lab wants to merge 1 commit into
ZhouYinLong-lab wants to merge 1 commit into
Conversation
The previous example was missing the required 'type' declaration and used plain strings instead of proper JSON Schema property objects. Fixes #128
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.
What changed
Fixed the
inputSchemain theTooldocumentation example to produce a valid JSON Schema.Why
The previous example was invalid JSON Schema:
"type": "object"declaration{ type, description }objectsUsers who copy-pasted the example would get schema validation errors from MCP clients.
Verification
The corrected schema follows the JSON Schema specification for objects with properties, matching the pattern documented in the issue discussion.
Related issue
Fixes #128