Skip to content

fix(mcp): Make all input schemas valid for Gemini. #8537

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 12, 2025
Merged

Conversation

mbleigh
Copy link
Contributor

@mbleigh mbleigh commented May 11, 2025

Gemini is currently not able to handle arbitrary key/value dictionaries, so I had to change some of the schemas around.

Gemini is currently not able to handle arbitrary key/value dictionaries,
so I had to change some of the schemas around.
Copy link
Contributor

@nohe427 nohe427 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Outside my one comment on json_values LGTM

@mbleigh mbleigh merged commit a0b7ea5 into master May 12, 2025
49 of 50 checks passed
@github-project-automation github-project-automation bot moved this from Approved [PR] to Done in [Cloud] Extensions + Functions May 12, 2025
@mbleigh mbleigh deleted the mb/mcp/schema-fixes branch May 12, 2025 17:20
blidd-google pushed a commit that referenced this pull request May 12, 2025
Gemini is currently not able to handle arbitrary key/value dictionaries,
so I had to change some of the schemas around.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants