Skip to main content
Glama

Validate and query JSON

inspect_json
Read-onlyIdempotent

Check whether a text is valid JSON (exact line and column of an error), or extract a value with a JSON Pointer (RFC 6901) such as /items/0/name; when the path breaks, says where and which keys exist.

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": {
      "json": "<json>"
    },
    "name": "inspect_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonYesThe JSON document as text.
pointerNoOptional RFC 6901 pointer; omit to only validate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely new behavioral detail: on validation failure it reports exact line and column, and on a broken pointer it reports where the path broke and which keys do exist. Since there is no output schema, this return-shape information is the main source of truth about responses.

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?

A single sentence that front-loads the primary validation mode before the extraction mode, with no filler or repetition. It is dense with parenthetical clauses, which slightly reduces scanability but every clause carries information an agent needs.

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

Completeness4/5

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

For a two-parameter, non-destructive read tool with no output schema and no nesting, the description covers both operating modes and the error-reporting behavior. The only remaining gap is whether successful validation returns a boolean or a structured result, a minor omission given the simplicity of the tool.

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 in the schema, including the 'omit to only validate' rule. The description contributes a concrete pointer example (/items/0/name) that illustrates the syntax, but otherwise restates the schema's meaning rather than extending it. Baseline 3 is appropriate.

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

Purpose5/5

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

The description names a specific verb and resource for each of the two modes: validity checking with error location, and value extraction via RFC 6901 JSON Pointer. No sibling tool in the catalog performs JSON validation or pointer extraction, so the tool is unambiguously distinguishable from the listed alternatives without opening the schema.

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

Usage Guidelines4/5

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

The description states the selection condition between the two modes clearly: supply a pointer to extract, omit it to only validate. That is effectively a when-to-use rule for each parameter combination. It does not name alternatives or exclusions, but no plausible alternative tool exists in this catalog for the same job.

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.