Skip to main content
Glama

csv_to_xlsx

Read-onlyIdempotent

Convert exact caller CSV to a real XLSX spreadsheet with one Data sheet and a SUM totals row. Explicit numericColumns and totalColumns; all other cells are literal strings, never inferred formulas. Returns actual file bytes. 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": {
      "csv": "<csv>",
      "numericColumns": "<numericColumns>",
      "totalColumns": "<totalColumns>"
    },
    "name": "csv_to_xlsx"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYes
totalColumnsYes
numericColumnsYes

Output Schema

NameRequiredDescriptionDefault
artifactsYes
sheetNamesYes
sourceSha256Yes
externalWritesYes

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?

Beyond annotations, the description discloses important behavior: the workbook structure, the SUM totals row, explicit numericColumns/totalColumns handling, and the fact that all other cells are literal strings with no inferred formulas. It also states that the tool returns actual file bytes, which is valuable behavioral context.

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?

The description is three compact sentences with the core output structure front-loaded, followed by parameter and formula behavior, then return type. The documentation URL is separated and does not clutter the operational explanation.

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?

The tool has an output schema and the description still clarifies the key return behavior (actual file bytes) alongside workbook structure and formula handling. It is mostly complete for a focused conversion tool, though it could better address input limits or error conditions.

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 description coverage is 0%, so the description must carry parameter meaning. It does explain that numericColumns and totalColumns are explicit and that all other cells are treated as literal strings, but it leaves some details inferential, such as the exact summing relationship for totalColumns and the CSV size constraints already present in the schema.

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?

The description gives a specific verb and resource: convert caller CSV into a real XLSX spreadsheet. It also names the output structure (one Data sheet plus a SUM totals row), which clearly distinguishes it from siblings like xlsx_to_csv and markdown_to_pdf.

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 usage is implied by the CSV-to-XLSX direction and the conversion details, but there is no explicit when-to-use, when-not-to-use, or alternative-selection guidance. It does not name xlsx_to_csv as the inverse operation or clarify when another conversion tool would be preferred.

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