The Model Context Protocol (MCP) has updated its tool schema specifications, notably changing the `structuredContent` field from an object with string keys to a more flexible `unknown` type. This change, outlined in proposal SEP-2106, allows tools to return arrays and primitives directly, but it introduces a source-breaking change for typed consumers. The MCP maintainers acknowledge this intentional break, emphasizing that the previous type was inaccurate when tools returned non-object data. This situation highlights the need for developers to treat tool schemas as strict API contracts, similar to OpenAPI, considering the broader surface area that includes descriptions and error messages, especially given that AI models consuming these schemas have less predictable upgrade behaviors than traditional API clients. AI
IMPACT Highlights the need for robust API contract management in AI tool integrations, impacting how developers build and maintain AI agents.
RANK_REASON Article discusses changes to a protocol for tool schemas and their implications for developers, rather than a new product release or frontier model.
- MCP
- Model Context Protocol
- November 25, 2025
- OpenAPI
- Representational State Transfer
- SEP-2106
- structuredContent
- TypeScript
AI-generated summary · Google Gemini · from 1 sources. How we write summaries →