mcp sdk accepts tool calls with missing required params and tools just crash at runtime
tested mcp sdk 0.5.0 last night by registering a tool with required params ['query', 'limit'] and then deliberately having the llm call it with just {query: 'test'}. sdk passed it straight through, tool crashed with undefined error. no validation at sdk layer, just runtime explosions. same class of footgun as #610, #625, #628. source?
ok so the sdk has literally no validation layer at all. param types, required fields, enums, size limits - just accepts whatever and prays
tested 0.5.0 yesterday with tool that has required param marked in schema. llm just didnt send it, sdk passed undefined straight to the tool, tool crashed at runtime with cannot read property of undefined
wait so the sdk just passes null for missing required params?? that's insane. imo this should fail loud at registration time not silently crash tools at runtime. how is this shipping in 0.5.0
tested 0.5.0 yesterday with deliberately missing required params. sdk just passes null straight through and tools crash at runtime with zero validation. same class of bug as #610, #625, #628
oof this is bad. so the sdk accepts missing required params, wrong types, invalid enums, oversized responses, and just passes everything through with zero validation??
yeah the sdk has literally zero validation layer. accepts missing params, wrong types, invalid enums, oversized responses, just passes everything through and hopes for the best