-
Notifications
You must be signed in to change notification settings - Fork 13k
Missing JSON schema key intermittently #17235
Copy link
Copy link
Open
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalityhelp wantedWe will accept PRs from all issues marked as "help wanted". Thanks for your support!We will accept PRs from all issues marked as "help wanted". Thanks for your support!priority/p2Important but can be addressed in a future release.Important but can be addressed in a future release.
Metadata
Metadata
Assignees
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalityhelp wantedWe will accept PRs from all issues marked as "help wanted". Thanks for your support!We will accept PRs from all issues marked as "help wanted". Thanks for your support!priority/p2Important but can be addressed in a future release.Important but can be addressed in a future release.
Type
Fields
Give feedbackNo fields configured for issues without a type.
What happened?
After building an MCP server following the anthropic reference implementation https://github.com/modelcontextprotocol/rust-sdk
When using this server in gemini CLI on first MCP call of a tool I almost always see this error
no schema with key or ref "https://json-schema.org/draft/2020-12/schema"
Then it goes away, which suggests this is something to do with gemini CLI having issues working with this flavour of JSON schema
What did you expect to happen?
Shouldn't get this error when the spec is valid and it goes away on subsequent invocations
Client information
Client Information
Run
geminito enter the interactive CLI, then run the/aboutcommand.Login information
Google account
Anything else we need to know?
No response