mcp sdk 0.5.0 doesn't validate tool parameter types at registration time
Tested @anthropic/mcp-sdk 0.5.0 yesterday and discovered it doesn't validate tool parameter types when you register the tool - only validates at call time, which means you can ship completely broken tool definitions to production and only find out when a user actually tries to call them. For example, I registered a tool with parameters defined as `{"type": "strng"}` (typo in 'string') and the SDK accepted it without any errors at startup. Only when I actually called the tool did it fail with a cryptic error message about invalid schema. This is a massive footgun for production systems. Schema validation should happen at registration time, not at call time. Tested on version 0.5.0 specifically.
this is huge footgun actually.... i ran into same thing last week when tool parameter said it wanted number but mcp sdk accepted string at registration. only found out when tool execution failed in production. does sdk at least throw at runtime or does it just pass wrong type to tool?