Burs-IA Utils

Construir tabla Markdown

markdown-table

Read-onlyIdempotent

Construye una tabla Markdown (GFM) desde objetos o filas, con alineación por columna. Cuándo: hay que leer, construir o revisar con exactitud una URL, una cabecera HTTP, un token, una versión, un rango de IP, un documento HTML o Markdown o un archivo para agentes. No para: extraer los títulos de un Markdown y genera una tabla de contenido anidada con anclas estilo GitHub (markdown-toc). 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: Builds a GitHub-flavored Markdown table from an array of objects (columns = union of keys) or an array of rows with headers, with per-column alignment and pipe escaping. When: a URL, HTTP header, token, version string, IP range, HTML or Markdown document or agent-readiness file has to be parsed, built or checked exactly. Not for: extracting ATX headings (markdown-toc). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description
`rows`	Yes	Array of objects or arrays (array of object/array; required).
`align`	No	Alignment per column (array of string; optional; default []; up to 100 items).
`headers`	No	Headers (for array rows or to order columns) (array of string; optional; up to 100 items).

Output Schema

Name	Required	Description	Default
`markdown`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / rows / examples

Added value: +[
+  [
+    {
+      "name": "Ana",
+      "score": 9.5
+    },
+    {
+      "name": "Luis|M",
+      "score": 8
+    }
+  ]
+]

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Builds a GitHub-flavored Markdown table from an array of objects (columns = union of keys) or an array of rows with headers, with per-column alignment and pipe escaping. When: a URL, HTTP header, token, version string, IP range, HTML or Markdown document or agent-readiness file has to be parsed, built or checked exactly. Not for: extracting ATX headings (markdown-toc). 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.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description still adds real value by stating determinism and hard limits (64 KB input, 1 s per call, 1 MB result), which no annotation conveys. It repeats 'no network, no stored state' that the annotations already imply, keeping 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The tool-specific content is front-loaded and tight, but the definition ships the same text twice (ES then EN, then again in the schema description) and carries a 'When' sentence irrelevant to this tool. Roughly half the words do not earn their place.

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?

An output schema exists, so return values need not be described; limits, determinism, escaping and the two input modes are all covered. The only real gap is a concrete usage example of when the union-of-keys behavior surprises an agent, and the mismatched 'When' text distracts rather than completes.

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 baseline is 3; the description goes further by explaining the semantics the schema does not: object-mode columns are the union of keys, and headers can both supply array-row headers and order columns. The per-column alignment behavior and pipe escaping are also stated, which the minimal schema field descriptions leave implicit.

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 concrete verb and artifact: builds a GitHub-flavored Markdown table from objects (columns = union of keys) or rows with headers, with per-column alignment and pipe escaping. The EN half makes the input-to-output mapping unambiguous, and the exclusion of markdown-toc separates it from the nearest sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Not for' clause names a concrete alternative (markdown-toc), which is genuinely useful routing. However the 'When' clause is boilerplate copied from other tools in the suite ('a URL, HTTP header, token, version string, IP range ... has to be parsed, built or checked exactly') and does not describe when to reach for a table builder rather than, say, markdown-render-html or csv-build.

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?