Skip to main content
Glama

excel_to_csv

Convert Excel .xlsx/.xls spreadsheets or a selected sheet into standard RFC 4180 CSV files for data exchange and processing.

Instructions

Export Excel spreadsheet (.xlsx/.xls) sheet to standard RFC 4180 CSV.

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": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "excel_to_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to the input Excel file
sheetNoOptional specific sheet name to export
outputYesPath to save the output CSV file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does add useful context by pinning the output to RFC 4180 (quoting/escaping conventions), but it never says what happens when 'sheet' is omitted (first sheet? active sheet?), whether an existing output file is overwritten, or what occurs on a missing sheet or unsupported file.

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?

A single front-loaded sentence with no filler; the format constraints are packed into the same sentence rather than padded out.

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?

For a simple three-parameter conversion tool with no output schema, the description covers the essential contract, but the unspecified default-sheet behavior and overwrite semantics are real gaps for a tool that writes a file to disk.

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 schema already documents all three parameters; baseline 3 applies. The description adds only the accepted input extensions (.xlsx/.xls) and the output format, and says nothing about how 'sheet' matching works (exact name? case sensitivity?) or what the default is.

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?

States a specific verb ('Export') and resource ('Excel spreadsheet sheet') plus the output format ('standard RFC 4180 CSV'), which implicitly separates it from excel_to_json and other converters. It stops short of explicitly naming a sibling, so an agent must infer the distinction from the format alone.

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?

Usage is only implied by the output format: use this when a CSV artifact is wanted. There is no explicit when-to-use, no mention of when to prefer excel_to_json, and no stated prerequisites such as the input file existing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.