Burs-IA Utils

Omitir claves de JSON

json-omit

Read-onlyIdempotent

Elimina las claves indicadas de un objeto; con deep=true en todos los niveles. Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: devolver un objeto con solo las rutas indicadas (json-pick). 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: Removes the given keys from an object; with deep=true removes them at every nesting level (e.g. strip password or token fields). When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: returning a new object containing only the given dotted paths (json-pick). 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
`deep`	No	Apply recursively (boolean; optional; default false).
`keys`	Yes	Keys to remove (array of string; required; at least 1 items; up to 500 items).
`value`	Yes	JSON value (any JSON value; required).

Output Schema

Name	Required	Description	Default
`value`	No	any JSON value
`removed`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedInput schema / properties / keys / examples
```
Added value: +[
+  [
+    "token"
+  ]
+]
```

addedInput schema / properties / value / examples

Added value: +[
+  {
+    "a": 1,
+    "n": {
+      "token": "y"
+    },
+    "token": "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, no network, idempotent, and non-destructive behavior, and the description reinforces this with side-effects: none, no stored state, and deterministic output. It also adds operational limits: 64 KB input, 1 s per call, and 1 MB result.

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?

The content is front-loaded and organized into clear sections: purpose, when to use, when not to use, side effects, determinism, and limits. The main conciseness cost is the full Spanish/English duplication, which repeats the same information for a single-language reader.

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?

Given the rich annotations, 100% schema description coverage, and presence of an output schema, the description covers everything an agent needs: purpose, alternative, side effects, determinism, and limits. No important behavioral or selection information is missing.

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%, so the schema already documents the parameters, establishing a baseline of 3. The description adds helpful meaning for deep=true by explaining removal at every nesting level and gives a concrete password/token stripping example, though it does not add much beyond that for value or keys.

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 states a specific verb and resource: removes given keys from an object, with deep=true removing them at every nesting level. It also distinguishes the tool from the sibling json-pick by explicitly saying it is not for returning only the given paths.

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?

It gives explicit guidance under 'When' and 'Not for', naming the alternative json-pick and the condition that selects it. The structured-data examples (JSON, CSV, YAML, XML, arrays) further clarify the intended context.

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?