{"version":"2.1.290","anchor":"tool-inputschema-size-limit-removed","canonical_anchor":"tool-inputschema-size-limit-removed","heading":"Large tool input schemas are no longer rejected for their size","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/tool-inputschema-size-limit-removed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Large tool input schemas are no longer rejected for their size\n\nClaude Code no longer rejects a tool's input schema for being too long and only checks that it is JSON data\n\n**Unclear.** A size limit may still be enforced somewhere else.\n\n**What**\n\nA tool's input schema describes what input the tool accepts. Before, Claude Code rejected a schema that was over a character limit once written out as text. It no longer checks the size here. It only checks that the schema is JSON data.\n\n**Why**\n\nTools with very large input schemas are no longer turned away at this point.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}