Skip to content

fix(mcp): detect Gemini custom endpoints for proper tool response formatting#91

Open
paychex-inder wants to merge 1 commit intomainfrom
fix/gemini-custom-endpoint-detection
Open

fix(mcp): detect Gemini custom endpoints for proper tool response formatting#91
paychex-inder wants to merge 1 commit intomainfrom
fix/gemini-custom-endpoint-detection

Conversation

@paychex-inder
Copy link
Collaborator

Extended isGoogle check to include custom endpoints with 'gemini' or 'google' in the provider name. This fixes the 'Proto field is not repeating, cannot start list' error on second tool call when using custom Gemini endpoints via Kong gateway or other proxies.

Custom Gemini endpoints need text extraction from array responses just like native Google providers.

…matting

Extended isGoogle check to include custom endpoints with 'gemini' or 'google'
in the provider name. This fixes the 'Proto field is not repeating, cannot
start list' error on second tool call when using custom Gemini endpoints
via Kong gateway or other proxies.

Custom Gemini endpoints need text extraction from array responses just like
native Google providers.
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.

1 participant