Skip to main content
Glama

json-to-csv

POST a JSON array of flat objects (or {"rows":[...]}) and get CSV back. Columns are the union of all keys in order of first appearance. Values are quoted and escaped per RFC 4180. Nested objects are stored as JSON text. Up to 5000 rows per call. Free: 3 calls a day per visitor; after that $0.01 per call via x402 at https://tools.orchardshop.xyz/t/json-to-csv.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "json-to-csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description does the heavy lifting: it discloses the 5000-row-per-call cap, column ordering rules, escaping standard, and nesting behavior, plus the quota (3 free calls/day per visitor) and paid path ($0.01/call via x402 with a URL). It stops short of stating error behavior for malformed input or the response content type, so 5 is not warranted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Six tight sentences, each carrying new information, with the operation and output shape front-loaded before limits and pricing. No filler or repetition of the tool name.

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 single-parameter, stateless conversion tool with no annotations or output schema, the description covers input shapes, output format, edge-case handling for nesting, size limits, and access/pricing. Nothing an agent needs in order to call it correctly appears to be 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 0% and only one parameter exists, so the description must compensate, and it does: it explains that the body may be either a bare JSON array or a {"rows":[...]} wrapper, which the schema alone does not convey. It does not state whether the parameter is required or what the {name, note} fields in the schema example signify.

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 conversion (JSON array in, CSV out) and adds the mechanics that define the operation: column set is the union of all keys in first-appearance order, RFC 4180 quoting, nested objects flattened to JSON text. An agent can tell immediately this is the inverse of csv-to-json and what output shape to expect.

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 usage context is implied by the inputs described (flat objects, optional rows wrapper, 5000-row cap), but there is no explicit when-to-use/when-not guidance or pointer to a sibling for the reverse direction. Adequate but leaves routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources