Skip to main content
Glama

csv-convert

CSV convert. A CSV document in, URL-encoded as the csv query parameter (up to 12,000 bytes), a conversion out: RFC 4180 parsing (quoted fields, escaped quotes, newlines in quotes), delimiter sniffing among comma, semicolon, pipe, and tab, a JSON records array keyed by header, and a rendered Markdown table of the same rows, with every statistic included. Price: $0.10 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": {
      "csv": "<csv>"
    },
    "name": "csv-convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYesThe CSV document to convert (up to 12,000 bytes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the 12,000-byte cap, RFC 4180 parsing rules, delimiter sniffing across four delimiters, and — critically — the $0.10 USDC-on-Base x402 pricing with an HTTP 402 response containing payment terms. The only weak spot is the vague phrase 'with every statistic included', which does not say what statistics are returned.

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?

It is dense and front-loaded: the transformation is described first, then the payment mechanics, so an agent can stop reading early if it only needs the shape. The single long run-on sentence and the trailing 'with every statistic included' clause cost it a point.

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 one-parameter, no-output-schema tool this is nearly complete — input limits, parsing behavior, both output forms, and the payment/auth requirement are all covered. Only the unspecified 'statistics' in the returned payload leaves a small gap.

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 the single parameter already documents the 12,000-byte limit, so the baseline is 3. The description adds the meaningful detail that the value is URL-encoded and passed as the csv query parameter, which is beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource (CSV in, converted JSON records array plus rendered Markdown table out), which lets an agent distinguish it from a sibling like json-to-md. It does not name a sibling explicitly, so it stops just short of a 5.

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?

Usage is implied by the input/output shape (feed a CSV document, get JSON records and a Markdown table), but there is no explicit when-to-use statement, no exclusions, and no pointer to an alternative for the reverse direction or for large inputs.

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