You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
SEP-2106: Tools inputSchema & outputSchema Conform to JSON Schema 2020-12 #1000
Hi! I’d like to help with this issue, but I’d like to confirm the remaining scope before coding.
Since this issue was opened, #1170 has been merged, adding the io.modelcontextprotocol.modern server. Its tool feature validates input and output schemas, and the checked-in conformance report records 8/8 checks for json-schema-2020-12, including composition and conditional keywords. Those checks are currently marked as not scored, and the fixture appears to focus on input schemas. Earlier PRs #551, #749, and #949 also added support for arbitrary structured content, map-based tool schemas, and JSON Schema 2020-12 meta-schema validation.
Could you clarify which SEP-2106 acceptance criteria remain and which API/version line should own them? I see the issue has the 2.2.0-M2 repository milestone, while its activity also places it in 3.x Planning. Should the remaining work target the legacy 2.x API, the modern 3.x server, or specific uncovered cases? For example, should explicit structuredContent: null and the $ref security/resource-limit requirements be part of this issue?
I’d be happy to take a scoped piece once the target is clear.
Activity
wskr00 commentedon Oct 24, 2026
Hi! I’d like to help with this issue, but I’d like to confirm the remaining scope before coding.
Since this issue was opened, #1170 has been merged, adding the
io.modelcontextprotocol.modernserver. Its tool feature validates input and output schemas, and the checked-in conformance report records 8/8 checks forjson-schema-2020-12, including composition and conditional keywords. Those checks are currently marked as not scored, and the fixture appears to focus on input schemas. Earlier PRs #551, #749, and #949 also added support for arbitrary structured content, map-based tool schemas, and JSON Schema 2020-12 meta-schema validation.Could you clarify which SEP-2106 acceptance criteria remain and which API/version line should own them? I see the issue has the 2.2.0-M2 repository milestone, while its activity also places it in 3.x Planning. Should the remaining work target the legacy 2.x API, the modern 3.x server, or specific uncovered cases? For example, should explicit
structuredContent: nulland the$refsecurity/resource-limit requirements be part of this issue?I’d be happy to take a scoped piece once the target is clear.