Burs-IA Utils

Elegir claves o rutas de JSON

json-pick

Read-onlyIdempotent

Devuelve un objeto con solo las rutas indicadas (p. ej. user.name). Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: aplanar objetos y arreglos anidados en un nivel con claves con puntos (json-flatten-paths). 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: Returns a new object containing only the given dotted paths (e.g. user.name, items.0.id) from the input object. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: flattening nested objects/arrays into one level with dotted keys (json-flatten-paths). 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
`paths`	Yes	Dotted paths to keep (array of string; required; at least 1 items; up to 500 items).
`value`	Yes	Object (any JSON value; required).

Output Schema

Name	Required	Description	Default
`value`	No	any JSON value

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedInput schema / properties / paths / examples

Added value: +[
+  [
+    "id",
+    "user.name"
+  ]
+]

addedInput schema / properties / value / examples

Added value: +[
+  {
+    "extra": true,
+    "id": 1,
+    "user": {
+      "name": "Ana",
+      "pw": "x"
+    }
+  }
+]

First observedNov 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only, non-destructive, idempotent, and non-open-world behavior. The description adds useful operational context beyond annotations, including no network access, no stored state, deterministic output, and concrete limits of 64 KB input, 1 second per call, and 1 MB result size.

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 description is front-loaded and clearly structured with labels for definition, usage, exclusions, side effects, determinism, and limits. It loses some conciseness because the same information is duplicated in Spanish and English, but each language block is efficient.

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 two-parameter, read-only JSON transformation tool with full schema coverage, annotations, and an output schema, the description supplies everything needed: purpose, when to use, exclusions, side effects, determinism, and limits. No important behavioral context appears 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 both parameters well. The description adds meaningful path syntax examples such as user.name and items.0.id, clarifying dotted-path semantics beyond the terse schema text.

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: it returns a new object containing only the given dotted paths from the input object. It also gives concrete path examples and explicitly contrasts itself with json-flatten-paths, so an agent can distinguish it from that sibling.

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?

It provides an explicit "When" condition and a clear "Not for" exclusion naming json-flatten-paths. However, it does not distinguish itself from other closely related siblings such as json-extract, json-omit, or json-path, leaving some alternative-selection inference to the agent.

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?