Skip to main content
Glama

Diff JSON

bursia_json_diff
Read-onlyIdempotent

Compare two JSON documents and list added, removed and changed paths (max 500). Pure computation, free.

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": {
      "before": "<before>",
      "after": "<after>"
    },
    "name": "bursia_json_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterYesThe changed JSON text.
beforeYesThe original JSON text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / after / description
      Added value: +"The changed JSON text."
    • addedInput schema / properties / before / description
      Added value: +"The original JSON text."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: a hard cap of 500 listed paths and that it is 'pure computation, free' (no cost or external dependency). It does not say how invalid JSON input is handled, which keeps it below a 5.

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

Conciseness5/5

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

A single sentence with the core operation front-loaded, followed by the output shape and the practical limits. No filler or repetition.

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?

There is no output schema, and the description does the necessary work by describing the return value (added/removed/changed paths) and its 500-item truncation. The main remaining gap is error behavior on malformed JSON, which matters for a text-in 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% with two clearly documented parameters (before = original JSON text, after = changed JSON text), so the baseline is 3. The description only restates 'two JSON documents' and adds no format, size or encoding constraints beyond the schema.

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?

States a specific verb ('Compare') and resource ('two JSON documents') and even names the shape of the result: added, removed and changed paths. Against siblings like bursia_json_validate, bursia_json_path, bursia_json_format and bursia_json_to_csv, this is unmistakably the diff tool.

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

Usage Guidelines3/5

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

The purpose implies when to use it (comparing two JSON texts), but there is no explicit when-to-use guidance, no exclusions, and no pointer to alternatives such as json_path for querying or json_validate for checking validity. Usage is inferable but not stated.

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