Discussion: Schema's problem

[jokemanfire]

• Regarding whether the draft strictly follows the official schema https://json-schema.org/draft-07/schema
• The schema library we are currently using is relatively new. Is there a more mature alternative, or should we identify this repository and iterate on it

[jokemanfire]

Discussion on the official spec file

[jokemanfire]

And it is uncertain whether the schema third-party library currently in use strictly follows draft implementation.

[samscott89]

Adding a few observations here:

The schema library we are currently using is relatively new. Is there a more mature alternative, or should we identify this repository and iterate on it

In my experience schemars is one of the more mature/robust schema generators. However, there has been some sporadic maintenance since it's primarily maintained by a single person in their free time. But there are mature applications that depend on it like Oso, Zed, and cargo itself.

I think the main thing to look out for is this issue + path to 1.0.

Relatedly, and regarding:

Regarding whether the draft strictly follows the official schema https://json-schema.org/draft-07/schema

I ran into this issue with a MCP server built using this repo (main branch) with claude code. Related to this issue: anthropics/claude-code#586.

According to the schemars 0.8 docs the default schema conforms to draft07. However, when using this with Claude Code, it fails because Claude is expecting draft2020_12. For the record, it works fine with inspector.

As an experiment, I tried migrating rmcp to use the 1.0 prerelease of schemars. It was pretty easy and with that change my MCP server now works with Claude Code (and still works with inspector).

[jokemanfire]

@samscott89 Thank you for your summary, now I think the main problem is still focused on MCP's spec specification, which has too unclear a description of the schema . Although spec is based on draft 07 or draft 2020_12, it may add some adaptive modifications to it, but these are not described in the document.This can easily lead to misunderstandings in SDK development.
So my current idea is:

1. I will no longer consider the issue of schema libraries, as the problem itself is not caused by schema libraries. And especially for large projects like Zed that are using it.
2. For now, try to adapt to various clients as much as possible and use the most basic schema patterns until the official spec file is clear.

@4t145 @Hendler cc