Skip to main content
Glama

x420_csv_to-json

Parses RFC 4180 CSV with quoted fields, escaped quotes, embedded newlines, and custom delimiters into JSON rows keyed by header, with optional number/boolean type inference.

Instructions

CSV to JSON: Parses RFC 4180 CSV (quotes, escaped quotes, embedded newlines, custom delimiter) into JSON rows keyed by header, with optional number/boolean inference. Up to 500 KB and 10,000 rows. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.01 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: columns[], row_count, total_rows, truncated, ragged_rows, rows[] - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"text":"name,sqft,hail\nSmith,2400,true\n"Jones, R",1800,false"}.

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": {
      "text": "<text>"
    },
    "name": "x420_csv_to-json"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesCSV text
headerNofirst row is the header (default true)
max_rowsNo1–10000 (default 1000)
delimiterNofield delimiter (default ,; use tab or \t)
infer_typesNoconvert numbers/booleans (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.1/5.0
Behavior3/5

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

Beyond the annotations, the description adds substantial context: the tool is PAID at $0.01 USDC per call settled on Base via x402 using a wallet key, is real money, has hard size/row limits, and returns ragged_rows and truncated flags. That is meaningful disclosure of cost, settlement path, and degradation behavior. It stops short of describing error behavior (e.g., whether ragged rows pad, null, or fail) or who bears the cost on a failed parse, 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 definition is front-loaded with purpose, then limits, cost, and return shape, with the example last — a sensible order with no redundant sentences. The boilerplate 'Not professional, legal, insurance, engineering, medical, financial or tax advice' disclaimer is the one element that does not help an agent invoke the tool correctly.

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?

With no output schema, the description carries the burden of describing returns and does so explicitly (columns[], row_count, total_rows, truncated, ragged_rows, rows[], plus receipt and settlement transaction). Limits and payment mechanics are also covered. The remaining gap is failure/edge-case semantics, such as how ragged_rows and truncated manifest in the response.

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 schema already documents each parameter, establishing a baseline of 3. The description adds value beyond it by specifying the CSV dialect nuances (quotes, escaped quotes, embedded newlines, custom delimiter) and by giving a concrete example input that shows the expected shape of the required text field.

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 description opens with a specific verb and resource: 'CSV to JSON: Parses RFC 4180 CSV ... into JSON rows keyed by header, with optional number/boolean inference.' It names the exact format standard and the transformation target, which no sibling tool covers, so an agent can identify it immediately 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?

It provides clear operating context: RFC 4180 compatibility, a 500 KB / 10,000 row ceiling, and a concrete example input showing when the tool fits. It does not name an alternative or explicitly state when not to use it, though the size cap functions as an implicit boundary.

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