Claude Code MCP client rejects omitted optional params, deadlocks mutually-exclusive tool groups
jamescra · ghdev · 2026-09-16
Issue #94718 on anthropics/claude-code reports that MCP tool calls omitting optional parameters are rejected with Zod-style nonoptional/undefined errors even when the tool's JSON Schema declares a default.
- Explicitly passing the parameter (even null/empty) works, but tools enforcing "exactly one of A or B" or "X must be omitted when Y is set" hit a genuine deadlock: the client requires every optional field, while the tool's own logic rejects its presence. Some actions (HACS updateinformation, entity-registry lookups) are currently uncallable
- Reproduced on two different Home Assistant instances and ha-mcp versions 8.4.2/8.4.3, ruling out the server and pointing at the client-side validation layer
More from coding & agent
- Diorama gives OpenAI Codex coding agents a visual office you can watch work in real time — davidfromkansas · 2026-09-17
- Code-first, UI on top: building bespoke brand design tools with AI — floguo · 2026-09-17
- Study of 7 models across Claude Code, Codex, Pi: harness barely affects success but swings cost — DavideCrapis · 2026-09-17
- AI trading bot built with Jev is down 85%, owner shrugs it off — generativist · 2026-09-17
- Redditor's 3-Day SoL-Pi Test: Memory Objects Save ~12k Tokens Per Tool Run — Garblyx · 2026-09-17
- Reviewing AI code through Steve Jobs' lens: unseen internals deserve beauty too — sergeykarayev · 2026-09-17