Problem/Motivation

When using the MCP feature with Gemini 2.5 Pro in Cursor it fails with the following error:

The argument schema for tool mcp_drupal_content_85d467739a1b4ba46a9b8c4c9516704c", is incompatible with gemini-2.5-pro-preview-05-06. Please fix the MCP server, disable the MCP server, or switch models.

Comments

roromedia created an issue. See original summary.

gagosha’s picture

gagosha commented

This is a strange one, as the spec itself is model agnostic. Will check.

gagosha’s picture

gagosha commented
Assigned: Unassigned » jibla
michaellander’s picture

michaellander commented

I was running into issues where the Gemini CLI schema validation is more strict than other clients. In my case, there were additional schema properties such as 'name' that I had to remove recursively and a missing parameters property in some cases.

This was happening when using MCP with AI Function Calls, and I did not get to go further than that yet.

gagosha’s picture

gagosha commented
Status: Active » Closed (cannot reproduce)

Can't reproduce this one. If there is any way to reproduce this, please write the steps down and I will investigate.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.