GenerateContentRequest.tools[0].function_declarations[9].parameters.properties[url].format: only 'enum' is supported for STRING type

[lstep]

After trying to add a remote extension, asking anything results in a error:

$ goose session --with-extension "uvx mcp-server-fetch"
starting session | provider: google model: gemini-2.0-flash-exp
    logging to /home/lstep/.config/goose/sessions/6eXIMLYh.jsonl


Goose is running! Enter your instructions, or try asking what goose can do.


( O)> what are your activated extensions?
◓  Processing pattern particles...                                                                                                 
2025-02-03T09:32:52.878954Z ERROR goose::agents::truncate: Error: Request failed: Request failed with status: 400 Bad Request. 
Message: * GenerateContentRequest.tools[0].function_declarations[9].parameters.properties[url].format: only 'enum' is supported
for STRING type

    at crates/goose/src/agents/truncate.rs:279

Ran into this error: Request failed: Request failed with status: 400 Bad Request. 
Message: * GenerateContentRequest.tools[0].function_declarations[9].parameters.properties[url].format: only 'enum' is supported for STRING type
.

Launching goose with goose session --with-extension "uvx mcp-server-fetch" . I also tried with the manual method, gives the same error.
uvx launched manually on CLi works fine:

$ uvx mcp-server-fetch --help
usage: mcp-server-fetch [-h] [--user-agent USER_AGENT] [--ignore-robots-txt]

give a model the ability to make web requests

options:
  -h, --help            show this help message and exit
  --user-agent USER_AGENT
                        Custom User-Agent string
  --ignore-robots-txt   Ignore robots.txt restrictions

Please provide following information:

• OS & Arch: Ubuntu 22.04.5 LTS
• Interface: CLI
• Version: 1.0.4
• Extensions enabled: conputercontroller,developer
• Provider & Model: provider: google model: gemini-2.0-flash-exp

[salman1993]

this is an issue with Google Gemini models and the fetch MCP server which uses the URI format in json schema, more details here: #1029 (comment)

If you disable the fetch extension/MCP server, that should fix it.