Skip to main content
Glama
Grist MCP Server
by nic01asFr

Download Attachment

download_attachment

Retrieves the content of a Grist document attachment by document ID and attachment ID, enabling access to stored files for processing or analysis.

Instructions

Télécharge le contenu d'une pièce jointe.

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

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
attachment_idYesL'ID de la pièce jointe

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.2
    • addedInput schema / properties / attachment_id / description
      Added value: +"L'ID de la pièce jointe"
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document"
  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, yet it discloses nothing about read-only nature, required permissions, size limits, or failure behavior. The phrase 'downloads the content' implies retrieval, but that inference is all the agent gets; fortunately the output schema covers the return shape.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than being genuinely well-structured for a tool with siblings.

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?

Output schema and full parameter coverage reduce what the description must carry, but with zero annotations the agent still lacks any behavioral or selection context. For a retrieval tool sitting among several attachment siblings, one bare sentence leaves important routing information unstated.

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% and both parameters carry their own descriptions, so the schema already documents doc_id and attachment_id. The description adds no additional meaning about parameter formats or relationships, which is the expected baseline when schema coverage is complete.

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 names a specific verb and resource (download an attachment's content), which is clearly distinct from metadata-oriented siblings such as get_attachment_info. It stops short of explicitly naming or contrasting with any sibling, so it lands at 4 rather than 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 when-to-use or when-not-to-use guidance. With siblings like get_attachment_info and list_attachments available, an agent gets no statement about when downloading content is the right call versus inspecting metadata or listing attachments.

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