Burs-IA Utils

JSON a CSV

csv-build

Read-onlyIdempotent

Convierte un arreglo de objetos en CSV (RFC 4180); columnas = unión de claves; puede neutralizar fórmulas de hoja de cálculo. Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: convertir CSV (csv-parse). 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: Converts an array of objects (or arrays) to RFC 4180 CSV; columns are the union of keys in first-seen order, nested values are JSON-encoded, and spreadsheet formula prefixes can be neutralized. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: parsing RFC 4180 CSV (csv-parse). 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
`data`	Yes	Rows (array; required).
`columns`	No	Explicit column order (array of string; optional; up to 1000 items).
`delimiter`	No	Delimiter (optional; one of: ,, ;, , \|; default ",").	,
`line_ending`	No	Line ending (optional; one of: , ; default "\n").
`escape_formulas`	No	Prefix cells starting with = + - @ with ' (boolean; optional; default false).

Output Schema

Name	Required	Description	Default
`csv`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / data / examples

Added value: +[
+  [
+    {
+      "age": 30,
+      "name": "Ana"
+    },
+    {
+      "name": "Pérez, Juan",
+      "tags": [
+        "a"
+      ]
+    }
+  ]
+]

First observedNov 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint/openWorldHint, so the safety profile is covered; the description still adds real value with concrete limits (64 KB input, 1 s per call, 1 MB output), determinism, and the absence of network or stored state. It stops short of describing error conditions (e.g., what happens when the 64 KB or 1 s limit is exceeded), which keeps it from a 5.

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 each section (purpose, when, not-for, side effects, determinism, limits) earns its place. The full Spanish/English duplication roughly doubles the length for identical information, which is a real cost even if it serves bilingual matching.

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?

An output schema exists, so return values need not be explained; the description covers what an agent still needs — scope, the sibling alternative, side effects, determinism, size/time limits, and the formula-escaping behavior. Nothing material is missing for correct invocation.

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 baseline is 3, but the description genuinely adds meaning beyond the schema: columns default to the union of keys in first-seen order, nested values are JSON-encoded, and escape_formulas prefixes cells starting with = + - @. Those are behaviors the schema's per-property text does not state.

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 first clause names a specific verb and resource ("Convierte un arreglo de objetos en CSV (RFC 4180)") plus the exact column-derivation rule. The EN restatement adds that arrays are also accepted, nested values are JSON-encoded, and formula prefixes can be neutralized, so the agent knows precisely what transformation is performed rather than a generic "convert".

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?

"Cuándo:" enumerates the situations this tool serves (transform, compare, or check structured data exactly), and "No para:" names the counterpart explicitly: parsing CSV belongs to csv-parse. That is an explicit when/when-not plus a named alternative, leaving nothing for the agent to infer.

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?