Skip to main content
Glama

xlsx_to_csv

Read-onlyIdempotent

Extract every sheet from a caller-supplied base64 XLSX into separate genuine UTF-8 CSV files, preserving sheet names in metadata and cell values. Formula values require existing caches; does not execute formulas. Refuses macros, external links and expansion bombs. Official documentation: https://creora.darwin.so/providers/files/docs

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": {
      "xlsxBase64": "<xlsxBase64>"
    },
    "name": "xlsx_to_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
xlsxBase64Yes

Output Schema

NameRequiredDescriptionDefault
artifactsYes
sheetNamesYes
sourceSha256Yes
externalWritesYes

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?

Annotations already cover readOnly, idempotent, non-destructive and closed-world, and the description still adds substantive behavior: macros, external links and expansion bombs are rejected, formulas are not evaluated and cached values are required, and sheet names are preserved in metadata. These are exactly the failure modes an agent cannot infer from the annotation set.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each doing distinct work: the operation, the formula caveat, the rejection policy. The core operation is front-loaded before caveats, and the docs link sits last where it belongs.

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?

An output schema exists, so return values need no prose, and annotations cover the safety profile. What remains for the description to carry — input format, formula behavior, and the security rejection boundary — is fully addressed.

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?

There is one parameter at 0% schema description coverage, so the description carries the burden and does clarify that xlsxBase64 is a caller-supplied base64-encoded XLSX. It does not mention the 174,764-character ceiling, which is the one constraint an agent could trip over, so it falls short of a 5.

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 plus resource ('Extract every sheet ... into separate genuine UTF-8 CSV files') with the source format (base64 XLSX) and the output granularity (one CSV per sheet). The direction of conversion is unambiguous, which alone distinguishes it from the inverse sibling csv_to_xlsx.

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 description supplies the preconditions that gate successful use ('Formula values require existing caches; does not execute formulas') and the input classes it refuses, which implicitly tells an agent when the call will fail. However, it never names csv_to_xlsx as the reverse alternative or states when a caller should choose one direction over the other, so selection guidance is only implied.

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