Skip to main content
Glama

Data Converter API - CSV, Excel, JSON both ways

data_convert
Read-onlyIdempotent

Convert CSV (any delimiter/encoding), Excel (xlsx/xls) or JSON (nested objects flattened to dot columns) into JSON, CSV or Excel. to=json also returns the rows inline as data. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.003 per call via x402 at https://radarbg.com/x402/data-convert.

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": {
      "to": "json",
      "fileName": "people.csv",
      "fileContent": "bmFtZSxjaXR5CkFubmEsQmVybGluCkl2YW4sVmFybmEK"
    },
    "name": "data_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNojson, csv or xlsxjson
filesNoOr several files: [{fileName, fileContent (base64)}]
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. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds operational context those annotations cannot convey: processing happens server-side, files are deleted immediately after the call with nothing stored, and there are rate limits (25 free calls/day per IP) plus per-call pricing via x402. The data-retention and quota disclosures are exactly the behavior an agent needs before sending a file containing user data.

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?

Front-loaded with the transformation matrix in the first sentence, then returns behavior, then privacy/quota/commercial terms, with no filler. The final billing sentence is somewhat dense (free tier, per-call price, x402 URL) but every element is operationally relevant to a caller.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description only explains the return for one case (to=json returns rows inline). For to=csv or to=xlsx it never says whether the caller receives base64 content, a download URL, or both, which is a meaningful gap for a file-producing tool. Privacy, limits, and pricing are otherwise well covered.

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 documents all four parameters, but its descriptions are terse (e.g. "json, csv or xlsx"). The description adds real meaning beyond the schema: nested JSON is flattened into dot columns, CSV accepts any delimiter/encoding, and to=json returns rows inline as data. It does not explain the files[] batch behavior beyond what the schema says.

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 (Convert) with both source formats (CSV any delimiter/encoding, Excel xlsx/xls, JSON) and target formats (JSON, CSV, Excel), so the transformation matrix is unambiguous. It is clearly distinct from the data-image siblings like image_convert or pdf_to_image because it operates only on tabular data formats.

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?

Usage context is clear: pick the tool when moving between CSV/Excel/JSON, and it notes that to=json additionally returns rows inline, which helps an agent decide which target format to request. It lacks explicit when-not-to-use guidance or named alternatives, but the conversion matrix effectively covers the selection decision.

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