Skip to main content
Glama

schema-witness

One valid and one invalid example for each constraint in a JSON Schema — Walks a caller-supplied JSON Schema 2020-12 and, for every constraint keyword (type, enum, const, minimum, maximum, exclusiveMinimum, exclusiveMaximum, multipleOf, minLength, maxLength, pattern, format, minItems, maxItems, uniqueItems, required, minProperties, maxProperties, additionalProperties false, dependentRequired), returns the JSON pointer of the constraint, an example that satisfies it and

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "schema": "<schema>"
    },
    "name": "schema-witness"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemaYesThe schema to generate examples for. Full JSON Schema 2020-12 (local $ref only).
maxConstraintsNoStop after this many constraints (default 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return shape (JSON pointer + valid + invalid example per keyword), which is valuable, and the schema field notes 'local $ref only' indicating external refs are unsupported. However, it says nothing about error behavior, unsupported/non-2020-12 keywords, determinism of generated examples, or what happens on truncation, and the sentence is cut off mid-thought.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first clause, which is good. But the body is one run-on sentence dominated by a 20-item keyword parenthetical, and the text is truncated mid-word ('...an example that satisfies it and'), which damages structure and leaves the key return element unfinished.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters and no output schema, the description must explain the return value — it starts to (pointer, satisfying example, and presumably a violating one) but is cut off before completing it. For a tool whose output shape is its whole reason to exist, an incomplete return description is a real gap, though the keyword enumeration partially compensates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented, setting the baseline at 3. The description adds only the framing that the schema must be JSON Schema 2020-12; maxConstraints is never mentioned in prose beyond what its schema field already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb+resource: it walks a caller-supplied JSON Schema 2020-12 and returns, per constraint keyword, the JSON pointer plus a satisfying and a violating example. The enumerated keyword list pins down scope precisely. It does not differentiate from siblings such as schema-compat or schema-repair, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance. Nothing says to prefer this over schema-repair (fixing a schema) or schema-compat (comparing schemas), even though all operate on JSON Schema. The use case is inferable from the output description but never stated as guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources