Skip to main content
Glama

excel_to_json

Convert Excel .xlsx/.xls spreadsheets into structured JSON while preserving cell types; optionally select a sheet, use headers, and save output to disk.

Instructions

Ingest Excel spreadsheet (.xlsx/.xls) into structured JSON with cell type preservation.

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>"
    },
    "name": "excel_to_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to the input Excel file
sheetNoOptional specific sheet name to extract
outputNoOptional destination path to save extracted JSON to disk
has_headersNoWhether the first row contains headers (defaults to true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose one genuine trait beyond the schema — 'cell type preservation' — but omits whether JSON is returned inline when no output path is given, how sheet-not-found or malformed files behave, and whether the source file is untouched.

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?

One front-loaded sentence with no filler; the format constraints and type-preservation promise arrive immediately. 'Ingest' is slightly softer than 'convert', but nothing is wasted.

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 four-parameter converter with no output schema, the definition is minimally adequate: the transform and its fidelity claim are stated. It leaves open the default return path and failure modes, which an agent needs to plan a call sequence.

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 coverage is 100%, so input, sheet, output, and has_headers are all documented in the schema, which sets the baseline at 3. The description adds no extra meaning about sheet matching rules (exact name vs index) or the default when 'output' is omitted.

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?

The description gives a specific verb and resource ('Ingest Excel spreadsheet') plus the exact output format (structured JSON) and accepted extensions (.xlsx/.xls). That clearly separates it from excel_to_csv and pdf_to_json, though it never names a sibling or states the boundary explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this over excel_to_csv (same source, different target) or office_to_markdown, and no mention of prerequisites such as the file existing or being password-free. The use case is only implied by the tool name.

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