Burs-IA Utils

Arreglo JSON a NDJSON

json-to-ndjson

Read-onlyIdempotent

Serializa un arreglo JSON como NDJSON (un valor por línea). Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: convertir JSON delimitado por líneas (ndjson-to-json). 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: Serializes an array of JSON values as newline-delimited JSON (one compact value per line). When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: parsing newline-delimited JSON (ndjson-to-json). 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
`values`	Yes	Values (array; required).

Output Schema

Name	Required	Description	Default
`ndjson`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / values / examples

Added value: +[
+  [
+    {
+      "a": 1
+    },
+    [
+      2
+    ],
+    "x"
+  ]
+]

First observedNov 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The safety profile (read-only, no network, no state) restates annotations rather than adding to them, but the limits block (64 KB input, 1 s per call, 1 MB output) and the determinism guarantee are genuine context the annotations do not carry. No return-format details, but an output schema exists.

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?

Labeled sections (Cuándo / No para / Efectos secundarios / Determinista / Límites) are front-loaded and scannable, with the sibling exclusion placed early. The full bilingual duplication roughly doubles length, though it stays tight per section.

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 a one-parameter, pure transformation with an output schema and full annotations, nothing needed to call it correctly is missing: scope, exclusion, side effects, determinism, and hard limits are all present.

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?

Only one parameter with 100% schema description coverage and an example, so the schema does the heavy lifting. The description adds no syntax, element-type, or nesting guidance beyond 'un valor por línea' — baseline 3 applies.

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 ('Serializa un arreglo JSON como NDJSON, un valor por línea') and immediately contrasts it with the inverse sibling ndjson-to-json. An agent can distinguish it from the dozens of other json-* siblings without opening the schema.

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?

Explicitly names the exclusion ('No para: convertir JSON delimitado por líneas (ndjson-to-json)'), which is the strongest routing signal. The positive 'Cuándo' clause is vaguer — 'transformar, comparar o revisar con exactitud datos estructurados' describes almost any serializer in this catalog.

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?