{"version":"2.1.246","anchor":"tool-inputs-with-untyped-schemas-are-parsed-instead-of-arriv","canonical_anchor":"tool-inputs-with-untyped-schemas-are-parsed-instead-of-arriv","heading":"Tool inputs with untyped schemas are parsed instead of arriving as text","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/tool-inputs-with-untyped-schemas-are-parsed-instead-of-arriv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Tool inputs with untyped schemas are parsed instead of arriving as text\n\nMCP and plugin tools with loose input schemas now get real data instead of stringified JSON.\n\n**What**\n\nMCP and plugin tools whose input schema omits `type` on a property were receiving stringified JSON where the model intended structured data. Such properties are now treated as accepting any type, and a string that decodes to a boolean, number, array or object is parsed.\n\n**Details**\n\n- The new case applies when a property's schema carries only annotation keywords: `$comment`, `default`, `deprecated`, `description`, `examples`, `readOnly`, `title`, `writeOnly`.\n- Properties that do declare array, object, boolean, number or integer were already re-parsed and are unchanged.\n\n**Evidence**\n\n`Error normalizing tool input`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}