Skip to main content
Glama
Grist MCP Server
by nic01asFr

Download Document Excel

download_document_excel

Downloads a Grist document as an Excel file, letting you export a specific table and choose header labels, IDs, or none.

Instructions

Télécharge un document Grist au format Excel.

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": {
      "doc_id": "<doc_id>"
    },
    "name": "download_document_excel"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
headerNoFormat des en-têtes (label, id, ou none)label
table_idNoL'ID de la table à exporter (optionnel, première table par défaut)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.2
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document"
    • addedInput schema / properties / header / description
      Added value: +"Format des en-têtes (label, id, ou none)"
    • addedInput schema / properties / table_id / description
      Added value: +"L'ID de la table à exporter (optionnel, première table par défaut)"
  2. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it adds almost nothing: it implies a read/export operation but says nothing about permissions, size or row limits, whether the export is synchronous, or what happens with very large documents. The existence of an output schema covers the return value, but the operational characteristics of the export remain undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words, but its brevity borders on under-specification rather than economy. It is well-formed, just not very informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three parameters, no annotations, and a download/export side effect, the definition should at least state the read-only nature and any access requirement. The output schema helps with return semantics, but an agent still lacks enough context to know when this export is appropriate or what it can fail on.

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 doc_id, header and table_id are already documented in the schema. The description adds no meaning beyond that, which makes the baseline 3 correct here.

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 sentence names a specific verb (Télécharge) and resource (un document Grist) plus the output format (Excel), so an agent can tell what the tool produces. It does not distinguish itself from siblings such as download_document_sqlite or download_table_csv, which is the only thing keeping it below a 5.

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 pick this over download_document_sqlite or download_table_csv, nor on prerequisites such as document access rights. The agent must infer the choice from the format keyword alone.

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