Replies: 2 comments 3 replies
-
-- from Claude :) Now I can see the issue! Looking at your MCP Tools component code, the problem is in the create_input_schema_from_json_schema function and how it handles array parameters. The error occurs when the MCP tool schema has an array parameter without proper items specification.
Solution 2: Check Your MCP Server Look at your command: uvx mcp-server-fetch Solution 3: Debug Which Tool is Problematic Check for problematic array fieldsif hasattr(tool, 'inputSchema') and tool.inputSchema:
Use in update_tools method:for tool in self.tools:
Quick Test |
Beta Was this translation helpful? Give feedback.
-
so its definitely something to do with how gemini parses the json tool output for jira_batch_get_changelogs, to work around this I explicitly exclude that from enabled-tools and it works completely fine. I am not expert enough in pydantic or python to really figure out the root of this issue. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to setup mcp-atlassian as toolset, and use gemini as my agent, however it always fails with this error and I can't figure out for the life of me how to move forward. I can create the mcp in langflow fine and list out the tools, but when I link it up to the agent is where it all goes wrong.
I suspect the issue actually lies within the MCP not producing the correct fields/items when listing tools, at least, not what gemini is expecting.
Beta Was this translation helpful? Give feedback.
All reactions