Skip to main content
Glama

CSV Splitter API - cut a big CSV or Excel file into parts

csv_splitter
Read-onlyIdempotent

Split a large CSV/Excel file into files of N rows each (header repeated), returned as separate files. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/csv-splitter.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rows": 2,
      "fileName": "big.csv",
      "fileContent": "YSxiCjAseAoxLHgKMix4CjMseAo0LHgK"
    },
    "name": "csv_splitter"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNoRows per file
filesNoOr several files: [{fileName, fileContent (base64)}]
formatNocsv or xlsxcsv
fileNameNoFile name with extension, e.g. report.pdf
fileContentNoThe file as base64 (a data: URI is fine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / rows / minimum
      Added value: +1
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that processing happens server-side, that files are deleted immediately with nothing stored, and that limits are 25 calls/day free or $0.005/call via x402 — real operational context an agent needs. The annotations only say readOnly/openWorld/idempotent; the retention and pricing details are the valuable addition. It stops short of describing the shape of the returned file list, which is the one behavioral gap.

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?

Three sentences, front-loaded with the core operation before privacy, limits, and pricing. Every sentence carries information, though the x402 URL is a long tail that could have been compressed.

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 five-parameter stateless utility with no output schema, the description covers purpose, retention, cost, and rate limits adequately. It could have mentioned the two input modes (single fileName/fileContent vs the files array) since there is no output schema and no required parameters to anchor the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameters self-document and the baseline is 3. The description only adds the meaning of 'rows' (row count per output file, with headers repeated); it says nothing about the alternate 'files' array input mode or the csv/xlsx format switch that the schema defines.

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 concrete verb and resource ('Split a large CSV/Excel file into files of N rows each') plus the key behavior that headers are repeated and results come back as separate files. This is specific enough to distinguish it from sibling converters like csv_to_vcard or excel_to_pdf, which change formats rather than partition a file.

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 phrase 'large CSV/Excel file' implies the use case (a file too big to handle in one piece), but there is no explicit when-to-use/when-not-to-use statement and no alternative tool is named. The agent must infer that this is the right choice from the word 'large' alone.

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