Burs-IA Utils

Leer con JSON Pointer (RFC 6901)

json-pointer-get

Read-onlyIdempotent

Lee el valor en una ruta como /clientes/0/nit dentro de un documento JSON con la sintaxis RFC 6901 (~1 es /, ~0 es ~) e indica si la ruta existe en lugar de fallar. Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: evaluar una consulta JSONPath (json-path). 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: Reads the value at a path such as /clientes/0/nit inside a JSON document using RFC 6901 syntax (~1 stands for /, ~0 for ~) and reports whether the path exists rather than failing. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: evaluating a JSONPath query (json-path). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`value`	Yes	JSON document (any JSON value; required).
`pointer`	Yes	JSON Pointer (string; required; up to 4096 chars).

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / pointer / examples
```
Added value: +[
+  "/a/b~1c/1"
+]
```
- addedInput schema / properties / value / examples
```
Added value: +[
+  {
+    "a": {
+      "b/c": [
+        10,
+        20
+      ]
+    }
+  }
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Reads the value at a path such as /clientes/0/nit inside a JSON document using RFC 6901 syntax (~1 stands for /, ~0 for ~) and reports whether the path exists rather than failing. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: evaluating a JSONPath query (json-path). 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."

First observedNov 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing that a missing path is reported rather than raising an error, that there is no network access and no stored state, that output is deterministic, and by giving concrete hard limits (64 KB input, 1 s per call, 1 MB result). These are exactly the operational constraints an agent needs before calling.

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 single-language block is front-loaded and well structured: purpose, example, when, not-for, side effects, determinism, limits. The cost is full duplication in Spanish and English plus a trailing meta-note referencing inputSchema.description, which adds token weight without new information.

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?

With an output schema present, return shape need not be described, and the description still covers scope, error behavior, side effects and limits. A minor gap is that it does not state what happens for a syntactically invalid pointer (as opposed to a non-existent path).

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% with per-property descriptions and examples, so the baseline is 3. The description earns above baseline by explaining RFC 6901 escaping (~1 for '/', ~0 for '~') and illustrating a nested array path, semantics not spelled out in the schema itself.

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 ('Reads the value at a path ... inside a JSON document'), names the standard (RFC 6901), and gives a concrete example path (/clientes/0/nit). It distinguishes itself from json-path by explicitly saying it is not for JSONPath evaluation.

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?

Provides an explicit 'When' scenario (exact transformation/comparison/checking of structured data) and an explicit 'Not for' exclusion naming the json-path sibling. It does not, however, differentiate from other close siblings such as json-extract, json-pick, or json-flatten-paths, which an agent may also consider for path-based reads.

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?