Skip to main content
Glama

Preview a JSON Merge Patch

bpj_apply_json_merge_patch
Read-onlyIdempotent

Apply RFC 7396 JSON Merge Patch. Null object members remove fields and arrays are replaced as a whole.

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": {
      "document": "<document>",
      "patch": "<patch>"
    },
    "name": "bpj_apply_json_merge_patch"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYes
documentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds real behavioral value by stating the two RFC 7396 mutation rules (null deletes a member, arrays are wholesale replaced), but it never says the tool returns the merged document rather than modifying an input, which is the one behavior an agent most needs clarified here.

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?

Two short sentences, front-loaded with the governing spec, with zero filler. Each clause conveys a distinct fact an agent needs.

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?

For a two-parameter pure-computation tool with no output schema, the definition is serviceable but leaves the crucial contract implicit: it does not state that the merged result is returned as a preview, nor what the return shape looks like. The RFC reference and annotations cover much of the rest, so the gap is meaningful but not disqualifying.

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 0%, so the description must carry the load; it partially does by explaining what the patch content means semantically (nulls remove members, arrays replace wholesale). It says nothing about the two parameters themselves — that both 'document' and 'patch' are JSON supplied as strings, that both are required, or how invalid JSON is handled — so the patch rule is the only semantic addition.

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 names a specific verb and spec: 'Apply RFC 7396 JSON Merge Patch', so an agent that knows RFC 7396 knows exactly the transformation being computed. It does not differentiate itself from the sibling bpj_plan_json_patch, and the verb 'Apply' sits in tension with the preview framing from the title, leaving slight ambiguity about whether a result is returned or a document mutated.

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?

Usage is only implied: the RFC reference tells the agent this is the tool for merge-patch semantic testing, and the rule 'Null object members remove fields and arrays are replaced as a whole' clarifies expected behavior. There is no explicit when-to-use, when-not-to-use, or pointer to the neighboring json-patch planner as the alternative.

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.