Burs-IA Utils

Crear JSON Merge Patch

json-merge-patch-create

Read-onlyIdempotent

Genera el JSON Merge Patch (RFC 7386) que convierte a en b. Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: aplicar un JSON Merge Patch (json-merge-patch-apply). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Generates the RFC 7386 merge patch that turns document a into b. Merge patches cannot set a value to null or patch inside arrays. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: applying an RFC 7386 JSON Merge Patch (json-merge-patch-apply). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB.

Input Schema

Name	Required	Description	Default
`a`	Yes	Source document (any JSON value; required).
`b`	Yes	Target document (any JSON value; required).

Output Schema

Name	Required	Description	Default
`patch`	No	any JSON value

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedInput schema / properties / a / examples

Added value: +[
+  {
+    "a": 1,
+    "b": {
+      "c": 1,
+      "d": 2
+    }
+  }
+]

addedInput schema / properties / b / examples

Added value: +[
+  {
+    "a": 1,
+    "b": {
+      "c": 3
+    },
+    "e": "x"
+  }
+]

First observedNov 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, and the description stays consistent while adding context annotations cannot express: determinism, the 64 KB input / 1 s / 1 MB output limits, and the semantic caveat that merge patches cannot set null or patch inside arrays. That caveat is exactly the kind of trap an agent needs warned about.

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?

Each language block is tightly front-loaded with purpose, usage, exclusions, side effects, determinism and limits. The only cost is that the entire content is duplicated in Spanish and English, roughly doubling length for an agent that reads both.

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

Completeness5/5

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

For a 2-parameter, read-only, deterministic tool with an output schema, everything an agent needs is present: purpose, alternatives, side-effect profile, runtime limits and the merge-patch semantic limitations. Nothing material is left to inference.

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

Parameters4/5

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

Schema coverage is 100% and the schema already names and exemplifies a and b, so the baseline is 3. The description still adds the directional framing ('convierte a en b') and, more importantly, the merge-patch semantics that a and b are compared under (nulls and array elements are not patchable), which shapes how the agent should supply the documents.

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 and resource ('Genera el JSON Merge Patch (RFC 7386) que convierte a en b') and anchors it to a named standard. It also explicitly names the sibling it is not for (json-merge-patch-apply), so the agent can separate create from apply without opening either schema.

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

Usage Guidelines5/5

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

Uses explicit 'Cuándo' / 'No para' sections: use it when structured data must be transformed, compared or checked exactly, and do not use it to apply a patch (pointing to json-merge-patch-apply). Both the inclusion and the exclusion condition are stated.

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

All Burs-IA Utils tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?