Repository navigation
Gemini tool calls format causing AI_APICallError #1052
Description
Hello,
Using Gemini 2.5 Pro I'm getting an AI_APICallError error every message I send to the LLM.
This is the error I got from my proxy
{"message":"Failed to parse request: failed to parse request: proto: syntax error (line 1:13263): unexpected token {","request_id":"5f","details":"failed to parse request: proto: syntax error (line 1:13263): unexpected token {"}
Looking at the payload and response from my proxy it seems that tools are passed as a dictionary and perhaps my proxy expects an array ?
This is what is sent by opencode
{
"tools":
{
"functionDeclarations": [
{
"name": string,
"description": string,
"parameters": {
object (OpenAPI Object Schema)
}
}
]
}
,
}
while https://cloud.google.com/vertex-ai/generative-ai/docs/model-reference/function-calling suggests tools should be an array such as
"tools": [
{
"functionDeclarations": [
{
"name": string,
"description": string,
"parameters": {
object (OpenAPI Object Schema)
}
}
]
}
],
But I dont know if this is an issue in opencode or if my proxy that should handle both use case so I decided to report it here first.
Thank you !
Metadata
Metadata
Assignees
Labels
No labels
Activity
jeanmatthieu commentedon Jul 21, 2025
Hi @necaris, thanks I have tied with version 0.3.46 and the issue still occurs on my end.
martinffx commentedon Aug 4, 2025
yes, also seem to be running into this. Gemini does not seem to be able to use my MCP Tools?
necaris commentedon Aug 4, 2025
Please see #1232 -- this is due to limitations in the Gemini API, so when MCP tools (or builtin ones) use JSON Schema elements that Gemini doesn't support, everything falls over.
rekram1-node commentedon Dec 28, 2025
[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
feat(commands): add santa-loop adversarial review command (anomalyco#…
revert(app): restore original session trace (anomalyco#1052)