MCP tools that declare a standard $schema no longer fail validation over that one key.
What's wrong with this entry?
A wrapper around the JSON-schema validator removes the $schema property when it names a recognised meta-schema and validates the remainder, so MCP tools declaring a standard $schema do not trip validation on that key.
- A trailing
#on the meta-schema URI is tolerated. - Only recognised meta-schema values are stripped; anything else is left in place.
- Whether this path is reached on every validation could not be resolved from the build.
$schema
Strings lifted out of the shipped bundle, so the claim above can be checked against them.