JSON Schema validation MCP. Keyless, offline: validate a JSON value against a JSON Schema (a practical draft-07 subset — type, required, properties, additionalProperties, items, enum, const, min/max, length, pattern, items counts, uniqueItems, and common formats). Returns each failure with its path. Pure logic — no API, no key.
Single tool with clear naming (validate_json_schema) and reasonable description (194 chars, within baseline 34-392 range). No output schema documented. Tool is read-only and offline, reducing error-handling complexity, but descriptions for 'data' and 'schema' parameters are minimal (under 20 chars for 'data'). No error recovery guidance or actionable error messages in implementation.
Validate a JSON value against a JSON Schema (draft-07 subset: type, required, properties, additionalProperties, items, enum, const, min/max, minLength/maxLength, pattern, minItems/maxItems, uniqueItems, format). Returns {valid, errors:[{path,message}]}. Keyless, offline.
Parameter 'data' lacks meaningful description. Current text 'The JSON value to validate (any type).' is under 20 chars of actionable guidance. Should explain what types are accepted and any constraints.
Output schema not documented. Callers cannot predict response structure (valid, error_count, errors array with path/message fields). LLMs need explicit output schema to plan downstream reasoning.
Parameter 'schema' description lacks format guidance. Should specify 'JSON Schema object (draft-07 subset: type, required, properties, additionalProperties, items, enum, const, min/max, minLength/maxLength, pattern, minItems/maxItems, uniqueItems, format)' to match tool capability.
Error handling returns schema errors as validation results (path: '$', message: 'schema error: ...') but does not guide LLM on recovery. Should distinguish between invalid input and malformed schema.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
Tool description embeds implementation details ('draft-07 subset') that belong in parameter docs. Main description should focus on WHAT and WHEN, not HOW.