You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all! I noticed some inconsistent behavior when switching models to google gemini regarding tool calls:
The same call works with either Anthropic or OpenAI but fails with Google.
If additionalProperties is provided to the tool parameter definition we receive the error response below, although this is a valid parameter in the JSON Schema definition and is accepted by OpenAI.
400 Invalid response received from google: [{"error":{"code":400,"message":"Invalid JSON payload received. Unknown name \"additionalProperties\" at 'tools[0].function_declarations[0].parameters'
If strict: true is specified in the tool definition we get the following error:
400 Invalid response received from google: [{"error":{"code":400,"message":"Invalid JSON payload received. Unknown name \"strict\" at 'tools[0].function_declarations[0]'
Lastly even after removing these parameters we still get an error and the gateway crashes:
TypeError: Cannot read properties of undefined (reading 'parts')
Additional information: running version 1.8.5 of the gateway locally using node.
What Should Have Happened?
Switching providers / model id should have been enough for making this request.
It should be possible to make tool calls to google gemini models
What Happened?
Hi all! I noticed some inconsistent behavior when switching models to google gemini regarding tool calls:
The same call works with either Anthropic or OpenAI but fails with Google.
If
additionalProperties
is provided to the tool parameter definition we receive the error response below, although this is a valid parameter in the JSON Schema definition and is accepted by OpenAI.If
strict: true
is specified in the tool definition we get the following error:Lastly even after removing these parameters we still get an error and the gateway crashes:
Additional information: running version 1.8.5 of the gateway locally using node.
What Should Have Happened?
Relevant Code Snippet
Your Twitter/LinkedIn
No response
The text was updated successfully, but these errors were encountered: