Skip to main content
Glama
Grist MCP Server
by nic01asFr

Download Table Csv

download_table_csv

Exports a Grist table as CSV by specifying document and table IDs, with optional header formatting.

Instructions

Télécharge une table Grist au format 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": {
      "doc_id": "<doc_id>",
      "table_id": "<table_id>"
    },
    "name": "download_table_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
headerNoFormat des en-têtes (label, id, ou none)label
table_idYesL'ID de la table

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"
  2. First observedv0.1.0

TDQS

C2.9/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 discloses almost nothing. It does not say whether the CSV is returned inline, as a URL, or as an attachment, nor whether row limits, permissions, or rate limits apply to the export.

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?

A single short sentence with no wasted words, and the core action is front-loaded. It is concise but borders on under-specification rather than being tightly structured for an agent's needs.

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?

The tool is a mutation-free export with three parameters and an output schema, so return values need not be explained. However, with no annotations and no usage or behavioral context, the definition leaves an agent without enough information to decide between this and the other download/export siblings.

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% — doc_id, table_id, and header are each documented in the schema, including the header enum-like values (label, id, none). The description adds no meaning beyond that, so the baseline 3 applies.

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 states a specific verb and resource: downloading a Grist table as a CSV file. It does not distinguish this from sibling export tools such as download_document_excel or download_document_sqlite, so an agent still has to infer which export format to choose.

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 when-to-use guidance, no mention of prerequisites (e.g., read permissions on the document), and no reference to alternatives. The only signal is the tool name itself, which the description merely restates.

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