Skip to content

[Bug]: Test MCP input fields are always as string #123

@exalsch

Description

@exalsch

Platform

Windows

Version

1.8.4

Bug Description

MCP tool call expects integer for a field (I have put 1 as there as input of course) but it get's send as string. Result: Error: MCP error -32602: MCP error -32602: Invalid arguments for tool list-calendars: [ { "code": "invalid_type", "expected": "number", "received": "string", "path": [ "top" ], "message": "Expected number, received string" } ]
It works fine when it get called during chat via the LLM.

Additional Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions