Skip to main content
Glama

csv-to-json

POST raw CSV as the body (first row is headers) and get back a JSON array of row objects, plus column names and row count. Handles quoted fields, commas and newlines inside quotes, and escaped quotes. Free: 3 calls a day per visitor; after that $0.01 per call via x402 at https://tools.orchardshop.xyz/t/csv-to-json.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
bodyYesPOST / with raw CSV text as the body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With zero annotations, the description carries the full behavioral burden and does well: it discloses the return shape, the parsing edge cases handled (quoted fields, embedded commas/newlines, escaped quotes), and a concrete quota ($0.01/call after 3 free per visitor via x402). Gaps remain around malformed-CSV errors and input size limits, but the core behavior is unusually well disclosed.

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?

Two sentences, front-loaded with the action and result, then edge cases, then pricing. No redundant or filler phrasing; the pricing tail is operationally relevant rather than padding.

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?

For a single-input converter with no output schema, the description covers input format, parsing guarantees, and return contents adequately. Only failure modes and payload limits are unaddressed, which is a minor omission given the tool's simplicity.

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% and there is only one parameter, so the baseline is 3. The description adds real meaning beyond the schema by specifying that the first row is treated as headers, which defines the semantics of the body content and the resulting keys.

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 transformation ('POST raw CSV' -> 'JSON array of row objects') and even enumerates the return shape (column names, row count). The conversion direction alone makes it unmistakable against siblings like json-to-csv.

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?

Conveys how to call it ('POST raw CSV as the body, first row is headers') but never says when to prefer it or when not to, and doesn't reference any alternative. Usage context is implied by the name/format rather than stated.

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