Skip to main content
Glama

Nalvorn Checks

json_schema_strict

Read-only

Validate JSON against a schema; returns exact error paths Free of charge.

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": "json_schema_strict"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemaYesJSON Schema document to validate against

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and nothing in the description contradicts it. The description does add one genuinely useful behavioral fact — that it 'returns exact error paths' — which matters since there is no output schema. However, it says nothing about how the JSON document under test is supplied, which is the main behavioral unknown.

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

Conciseness4/5

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

Front-loaded and very short, with the core action first and the return behavior second. The trailing 'Free of charge' is marketing noise that does not earn its place and slightly muddies the sentence structure.

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

Completeness2/5

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

For a validator, the essential fact an agent needs is how the JSON payload under test is provided; the description never says, and the schema's additionalProperties:true leaves it implicit. Combined with no output schema and no guidance on schema draft support, the definition is under-specified for a tool whose whole job is comparing two documents.

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?

With one parameter at 100% schema description coverage, the schema already documents 'schema' as the JSON Schema document. The description adds no syntax, draft-version, or format detail beyond that, and leaves unclear whether the JSON instance is passed as an additional property (additionalProperties is true) — a gap rather than added meaning.

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?

States a specific verb+resource ('Validate JSON against a schema') and is distinguishable from siblings like openapi_conformance or verify_manifest, which address different artifact types. It stops short of 5 because the phrasing implies two inputs (the JSON and the schema) while only the schema is named as a parameter.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives among the eleven sibling tools. The only additional clause is 'Free of charge,' which conveys nothing about selection or invocation.

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