Skip to main content
Glama

convert_spreadsheet

Convert spreadsheet and tabular data between formats such as CSV, TSV, JSON, Excel, HTML, and Markdown, with optional header, sheet, and delimiter controls.

Instructions

Convert spreadsheet and tabular data. Input: csv, tsv, json, jsonl, ndjson, xlsx (requires xlsx package). Output: csv, tsv, json, jsonl, html, markdown, xlsx.

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": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_spreadsheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetNoSheet name or index for xlsx input (optional)
headerNoFirst row is header (optional, default true)
skipRowsNoSkip N rows before header (optional)
delimiterNoCSV delimiter (optional, default ',')
inputPathYesAbsolute path to input spreadsheet file
outputPathYesAbsolute path for output file (include extension)
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format (auto-detected if not provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add useful context that xlsx input requires the xlsx package, but it omits that the tool writes a file to outputPath, whether existing files are overwritten, how errors surface, and any size/memory constraints — meaningful gaps for a file-mutating tool with zero annotation coverage.

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?

Two tight sentences, front-loaded with the purpose and then the input/output format facts. Nothing extraneous, no repetition of the tool name.

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 converter with 8 parameters, no output schema and no annotations, the description covers the core decision information (formats in and out, xlsx dependency). It falls short on write semantics and on the ods/xlsb omission, but those are the only notable holes.

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 all eight parameters are already documented; the description adds format-level context (and the xlsx package caveat) beyond the enums. However, its input list (csv, tsv, json, jsonl, ndjson, xlsx) omits ods and xlsb, which the inputFormat enum accepts, so it does not fully clarify parameter values.

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 concrete verb+resource ("Convert spreadsheet and tabular data") and then enumerates the accepted input and output formats, which immediately separates it from the other convert_* siblings (image, audio, document, archive, etc.). An agent can tell this is the tabular/spreadsheet converter without opening the schema.

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 format coverage implies when the tool applies, but there is no explicit guidance on when to prefer batch_convert, when to call get_supported_formats first, or what to do for non-tabular inputs. Usage is inferable rather than stated.

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