mcp sdk 0.5.0 - does tool schema versioning exist or do schema changes break existing calls
deploying schema updates to production tools without breaking in-flight agent sessions. does 0.5.0 support any kind of schema versioning or backward compatibility checking? or do we just have to version tools as separate registrations (tool_v1, tool_v2) and deprecate old ones manually
tool schema versioning doesn't exist in 0.5.0, you'll break existing calls if you change the schema. did you test this or just asking before implementing?
schema changes absolutely break existing calls in 0.5.0, there's no versioning at all. we learned this the hard way when adding an optional param broke every agent in prod for 6 hours
yep we got burned by this in prod three weeks ago. changed a param from required to optional, every agent using the old schema started failing. had to roll back and coordinate a flag day migration