Skip to main content
Glama

Jig

Server Details

Check JSON against a JSON Schema with exact paths, and schemas for OpenAI, Claude and Gemini strict.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools split cleanly along an obvious axis: one validates a *schema itself* (draft correctness plus OpenAI/Claude/Gemini compatibility), the other validates *data against a schema*. Each description explicitly negates the other's territory ("Not for ... checking whether a schema works with OpenAI, Claude or Gemini (jig_check_schema)"), leaving no realistic path to misselection.

Naming Consistency5/5

Both names use the same `jig_` namespace prefix and a snake_case verb_noun pattern (check_schema, validate_json). The verbs differ (check vs validate) but map meaningfully onto their distinct objects (schema vs json), so the pattern is predictable rather than accidental.

Tool Count4/5

Two tools is on the thin side of the typical 3-15 range, but the surface is deliberately narrow and each tool is a deep, self-contained capability rather than a thin wrapper. Adding a third tool would likely just split existing behavior, so the tight scope is defensible.

Completeness4/5

The core lifecycle for the domain is covered: schema-side linting, provider compatibility verdicts, auto-converted schemas, and instance validation with retry messages. Minor gaps remain — external $ref URLs are not fetched, $dynamicRef and some formats are unchecked, and syntax repair is explicitly out of scope — but each is disclosed as a workaroundable limitation rather than a dead end.

Available Tools

2 tools
jig_check_schemaCheck a JSON Schema, and whether OpenAI, Claude and Gemini strict modes accept itA
Read-onlyIdempotent
Inspect

Use when the user asks whether a JSON Schema is valid, or whether it will work with OpenAI Structured Outputs or function calling with strict: true, Claude structured outputs or strict tool use, or Gemini structured output (response_json_schema), or is writing a tool or function schema, an MCP inputSchema, a response_format, or a schema exported from Zod or Pydantic (signals: "Invalid schema for response_format", "strict mode error", "Claude returns 400 for my schema", "will this schema work with OpenAI", "Gemini ignores maxLength", "additionalProperties false", "all fields must be required"). First checks the schema against its draft: type names like "int", "required": true on a property, misspelt keywords, unresolvable $ref, invalid regex, impossible ranges. Then checks each provider's documented rules: OpenAI (every property in required, additionalProperties false on every object, root an object and not anyOf, no allOf/not/if, at most 5000 properties, 10 levels, 1000 enum values, documented formats only), Claude (additionalProperties false, no minimum/maximum/multipleOf/minLength/maxLength, minItems only 0 or 1, no recursion, at most 24 optional and 16 union-typed parameters per request, regex without lookarounds or backreferences), Gemini (minLength, maxLength, uniqueItems, minProperties and similar are dropped without an error). Returns per provider a verdict (ok, warnings, fails), each issue with its JSON Pointer path, rule, fix and the provider's doc URL, plus a converted copy the provider accepts (optional fields made required and nullable for OpenAI, unsupported constraints moved into descriptions the way the official SDK helpers do), and counts (properties, depth, optional and union-typed parameters). Example: {"schema":{"type":"object","properties":{"city":{"type":"string","maxLength":40},"days":{"type":"integer","minimum":1}},"required":["city"]},"providers":["openai","anthropic"]}. Rules are from each provider's docs, checked 2026-11-18; providers can change them, and very large schemas can still hit unpublished size limits.

Inputs: schema (required), draft, providers, include_converted.

jig_validate_jsonValidate JSON against a JSON Schema (every error with its path)A
Read-onlyIdempotent
Inspect

Use when the user asks whether some JSON matches a JSON Schema, or when JSON from a model reply, structured output, tool call, API response or file has to be checked against its schema before it is used or stored (signals: "validate this JSON", "does this match the schema", "which field is wrong", "the model returned bad JSON", "check the tool-call arguments", "why does my parser reject this"). Validates a JSON value (data), or raw model text (json_text: a ```json fence or prose around one JSON value is stripped; a syntax error comes back with line and column), against JSON Schema draft 2020-12, 2019-09, 07, 06 or 04, including $ref/$defs, anyOf/oneOf/allOf, if/then/else, unevaluatedProperties, patterns and formats (email, date-time, date, time, uuid, uri, hostname, ipv4, ipv6, duration). Returns valid true/false, every problem with its JSON Pointer path, keyword, expected and got values, and retry_message: a ready-to-send list of fixes for the model that produced the JSON. Example: {"schema":{"type":"object","properties":{"price":{"type":"number"}},"required":["price","sku"]},"data":{"price":"12.50"}}. Gives the expected answer on 6,018 of 6,227 official JSON-Schema-Test-Suite cases (ajv 8: 5,981); most misses are external $ref URLs, which are not fetched, $dynamicRef, and the idn-email, idn-hostname and iri formats, which are not checked. Not for repairing broken JSON syntax or for checking whether a schema works with OpenAI, Claude or Gemini (jig_check_schema).

Inputs: schema (required), data, draft, json_text, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Deterministic JSON validation and repair for AI agents. Validates, repairs, schema-checks, and diffs JSON so long-running agents don't corrupt their session state with malformed writes.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources