Skip to main content
Glama
Grist MCP Server
by nic01asFr

List Attachments

list_attachments

Retrieve attachments from a Grist document, with optional sorting and result limits, to inspect files linked to your data.

Instructions

Liste les pièces jointes d'un document Grist.

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": "list_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoColonne de tri (optionnel)
limitNoNombre maximum de résultats (optionnel)
doc_idYesL'ID du document

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 / limit / description
      Added value: +"Nombre maximum de résultats (optionnel)"
    • addedInput schema / properties / sort / description
      Added value: +"Colonne de tri (optionnel)"
  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?

With no annotations supplied, the description carries the full behavioral burden and discloses almost nothing: no mention of whether the listing is paginated, whether it requires document access, or what happens when a document has no attachments. "Liste" implies a read-only operation, but that is inference rather than disclosure.

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 reflects under-specification rather than disciplined editing.

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?

The tool is simple, its three parameters are fully described in the schema, and an output schema exists, so return values need no explanation. Still, the absence of any guidance on document access or relation to download_attachment leaves a real gap for a no-annotation tool.

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 sort, limit, and doc_id are already documented in the schema. The description adds no extra meaning about sorting semantics, default ordering, or how limit interacts with truncation, 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?

"Liste les pièces jointes d'un document Grist" gives a specific verb (list) and resource (attachments of a Grist document), so an agent knows exactly what it retrieves. It does not differentiate from siblings such as download_attachment, which keeps 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 when-to-use, when-not-to-use, or alternative routing guidance at all. The agent must infer that this is the metadata-listing counterpart to download_attachment from the name alone.

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