Skip to main content
Glama

Spreadsheet Cleaner API - trim, de-duplicate, merge Excel/CSV files

spreadsheet_cleaner
Read-onlyIdempotent

Clean one or many Excel/CSV files: trim spaces, drop empty rows/columns, remove duplicate rows (all columns or one key column), turn numbers-stored-as-text into numbers, merge files by column name. 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/spreadsheet-cleaner.

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": {
      "fileName": "list.csv",
      "fileContent": "TmFtZSxRdHkKIEFubmEgLDEKQW5uYSwxCiwKQm9iLDIK"
    },
    "name": "spreadsheet_cleaner"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoDuplicates by this column only (optional)
filesNoOr several files: [{fileName, fileContent (base64)}]
dedupeNoRemove duplicate rows
formatNoxlsx or csvxlsx
fileNameNoFile name with extension, e.g. report.pdf
dropEmptyNoRemove empty rows and columns
fixNumbersNoNumbers stored as text -> numbers
trimSpacesNoRemove extra spaces
fileContentNoThe file as base64 (a data: URI is fine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnly/openWorld/idempotent; the description goes beyond them with the retention guarantee ('files are deleted right after the call, nothing stored'), the rate limit (25 calls/day per IP) and the per-call pricing via x402. That is genuinely useful operational context. It misses failure modes and file-size limits, so not 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?

Operations are front-loaded in one dense clause, followed by the trust/retention statement and then the commercial terms, in a logical order with no filler. Slightly list-heavy but every sentence carries distinct information.

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 nine-parameter, no-output-schema tool with read-only annotations, the description covers what the operations do, that processing is server-side and stateless, and the cost model. The main gap is that with no output schema it never says what the response looks like (cleaned file as base64? a link?) or how multiple merged files are returned.

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 coverage is 100%, so the schema already documents all nine parameters and their defaults, making 3 the baseline. The description adds some meaning by explaining that de-duplication can key on 'all columns or one key column' and that merge is 'by column name', but it does not clarify the fileName vs files precedence beyond what the schema says.

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 leads with a specific verb and resource ('Clean one or many Excel/CSV files') and enumerates the exact operations: trim spaces, drop empty rows/columns, de-duplicate, coerce numbers, merge by column name. That is far more specific than the title. It stops short of a 5 because it never names a sibling it overlaps with (e.g. remove_duplicate_lines or csv_splitter), leaving the agent to infer the boundaries.

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?

It makes the input shape clear ('one or many' files, merge by column name), which implies when the tool applies, but gives no explicit when-not-to-use guidance or pointer to overlapping siblings such as remove_duplicate_lines or csv_splitter. Usage is implied from the operation list 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