MCP and plugin tools with loose input schemas now get real data instead of stringified JSON.
What's wrong with this entry?
MCP 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.
- The new case applies when a property's schema carries only annotation keywords:
$comment,default,deprecated,description,examples,readOnly,title,writeOnly. - Properties that do declare array, object, boolean, number or integer were already re-parsed and are unchanged.
Error normalizing tool input
Strings lifted out of the shipped bundle, so the claim above can be checked against them.