Skip to main content
Glama

X420 agent services

x420_csv_to-json

Read-onlyIdempotent

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. Price: $0.01 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: columns[], row_count, total_rows, truncated, ragged_rows, rows[].

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 observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: explicit size and row caps (500 KB, 10,000 rows), the $0.01 USDC x402-on-Base price, and the critical fact that the call returns payment instructions rather than the deliverable. It also discloses the paid response shape (columns[], row_count, total_rows, truncated, ragged_rows, rows[]). Annotations only say read-only/idempotent/open-world; the description carries the entire payment contract.

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?

Purpose and limits are front-loaded and the payment flow is ordered logically, but the description is dense and runs long. The sentence 'Not professional, legal, insurance, engineering, medical, financial or tax advice' is boilerplate that contributes nothing to invoking the tool and should be cut.

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 paid, multi-step x402 tool with no output schema, the description covers the transformation, its limits, the payment negotiation procedure, and the shape of the gated deliverable. Nothing an agent needs to call it correctly, or to interpret the payment response instead of treating it as data, is 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 100%, so the parameter meanings are already documented. The description goes modestly beyond by naming the parsing semantics (quotes, escaped quotes, embedded newlines, custom delimiter) and the 10,000-row ceiling that constrains max_rows, tying the parameters to concrete parser behavior.

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 verb and resource ('Parses RFC 4180 CSV ... into JSON rows keyed by header') plus the optional inference behavior, so an agent knows exactly what transformation happens. No sibling in the catalog performs CSV parsing, and the RFC 4180 qualifier disambiguates it from a generic converter.

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?

Gives clear operational context: this hosted endpoint does not pay and returns payment instructions, whereas the local x420-mcp server with a wallet key pays automatically. The step sequence (GET url, read PAYMENT-REQUIRED, retry with PAYMENT-SIGNATURE) is spelled out. It stops short of naming a non-payment alternative tool or stating when conversion should be avoided.

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