Skip to main content
Glama

SizeMyFile

Spreadsheet to CSV, JSON or Parquet

sheet_export
Idempotent

Export one Excel or ODS worksheet as a portable table. Select the worksheet and use its first row as column names. Up to 32 MiB input, 50,000 rows and 200 columns. CSV cells remain strings unless an operation explicitly parses numeric values. No uploaded code is executed. Formatting, formulas and workbook features are not preserved. Cached cell values are exported. Queues a run and returns its ID for progress and output tracking. Uses cloud allowance.

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": {
      "artifacts": "<artifacts>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "sheet_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNo
artifactsYes
idempotency_keyYes
allow_server_fallbackNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description adds substantial behavior beyond the annotations: hard limits (32 MiB, 50,000 rows, 200 columns), that formatting/formulas are dropped, that cached values are exported, that CSV cells stay strings, that no uploaded code runs, and that it queues an async run returning an ID and consumes cloud allowance. The only gap is that the meaning of 'allow_server_fallback' and the idempotency contract are never addressed.

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?

Sentences are short, front-loaded and each carries a distinct fact (scope, limits, data fidelity, execution model, cost). Nothing is redundant or padding.

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?

An output schema exists so return values need not be explained, and the description covers conversion fidelity and async execution well. However, for a tool with required, undescribed parameters and a nested options object, the unexplained artifacts/idempotency/fallback semantics leave real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 the burden, and it only clarifies 'sheet' (first row as column names) and indirectly 'format'. It says nothing about 'artifacts' (a required list of up to 50 UUIDs), 'idempotency_key' (required, 8-100 chars), or 'allow_server_fallback', all of which are non-obvious.

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 and resource ('Export one Excel or ODS worksheet as a portable table') and names the output formats in the title, so an agent can distinguish it from viewing tools like sheet_view or generic converters. Scope ('one worksheet') and constraints are concrete.

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 implied by the input type (Excel/ODS worksheets) and the size limits, but there is no explicit guidance on when to pick this over sheet_view or data_convert, and no stated prerequisites or exclusions. An agent must infer the routing decision.

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.