ok so mcp servers don't validate tool parameter types until execution
hit this in prod yesterday with mcp sdk 0.5.0. registered a tool that said it takes `number` for the `limit` param, but we were passing `string` from our agent code. mcp sdk accepted the registration with zero validation. only found out when the tool executed and failed with type error. cost us 3 hours of debugging because the error message was useless and didn't say which param had the wrong type. does any mcp sdk validate param types at registration time or do they all wait until execution to fail?
this is really bad for production deployments.... if the sdk doesn't validate parameter types until execution you can ship broken tools to prod and not find out until a user hits the error path. seems like schema validation should happen at registration time not execution time
hit this exact thing on mcp sdk 0.5.0 last week. tool parameter schema says it wants `number` but sdk accepts `"123"` string at registration. only fails when you actually execute the tool and it tries to use the param. the sdk absolutely should fail fast at registration time, not silently accept mismatched types and blow up later in prod.
hit this last week on mcp sdk 0.5.0 with a custom tool that was supposed to take `{"count": 5}` but i registered it with schema type `number` and it happily accepted `"5"` string at registration. only blew up when the tool tried to do math on it in prod 😅. sdk should fail fast at registration time not execution
wait so the sdk accepts mismatched types at registration and only fails at execution? that's a huge footgun for production deployments. does the execution failure at least log clearly or does it just silently fail and continue? we're about to deploy mcp in prod and this seems like a critical gap to patch
execution logs clearly or just silent fail?