MCP problem

[GreatInsight3139]

What happened

Headline: every MCP tool that takes arguments is uncallable; every zero-arg tool on the same server works. Two independent servers affected, so it's client-side.

I re-ran the repro live rather than quoting session memory, which produced the sharpest evidence:

• tokennuke__list_repos (zero args) → full 34-repo payload. Server, handshake, and transport are fine.
• tokennuke__index_folder with path → Original tool call input: {} .

Three details in that traceback are what make the report actionable:

1. {} — the arguments were never transmitted.
2. The error is Zod-shaped ( code: "invalid_type" , path as string array). tokennuke is Python — a pydantic error would look nothing like it. So the TypeScript client rejected the call before the server ever saw it.
3. The client holds a richer schema than it advertises. On ctx_execute it enforces a full 12-value language enum, yet the tool definition presented to me exposes properties: {} . The description documents path: Absolute path to the directory to index while the schema offers zero properties — so the tool is uncallable by construction, not by my error.

Steps to reproduce

Headline: every MCP tool that takes arguments is uncallable; every zero-arg tool on the same server works. Two independent servers affected, so it's client-side.

I re-ran the repro live rather than quoting session memory, which produced the sharpest evidence:

• tokennuke__list_repos (zero args) → full 34-repo payload. Server, handshake, and transport are fine.
• tokennuke__index_folder with path → Original tool call input: {} .

Three details in that traceback are what make the report actionable:

1. {} — the arguments were never transmitted.
2. The error is Zod-shaped ( code: "invalid_type" , path as string array). tokennuke is Python — a pydantic error would look nothing like it. So the TypeScript client rejected the call before the server ever saw it.
3. The client holds a richer schema than it advertises. On ctx_execute it enforces a full 12-value language enum, yet the tool definition presented to me exposes properties: {} . The description documents path: Absolute path to the directory to index while the schema offers zero properties — so the tool is uncallable by construction, not by my error.

Where does this happen?

CLI (terminal client)

Operating system

Windows

Version

0.0.174

Model

No response

Logs or screenshots

[dvelm]

you can use my version that has errors fixed and mcp works with all models https://github.com/dvelm/freebuff/releases