Skip to main content
Glama
Grist MCP Server
by nic01asFr

Get Attachment Info

get_attachment_info

Retrieves metadata for a Grist attachment by document ID and attachment ID, helping you identify file details before downloading or managing it.

Instructions

Obtient les métadonnées 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": "get_attachment_info"
  }
}

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 only says it retrieves metadata. It does not state that the operation is read-only, what permissions or scopes are required, or what happens when the attachment or document does not exist.

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 short sentence with no wasted words and the key noun front-loaded, but the brevity reflects under-specification rather than efficient completeness.

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 described, and the simple two-parameter read makes the definition minimally viable. However, with no annotations and no behavioral notes on failure modes or permissions, it leaves gaps an agent may hit at invocation time.

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% with only two required parameters (doc_id, attachment_id), so the schema already explains both. The description adds no meaning about ID formats or scoping beyond what the schema provides, so the baseline of 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?

States a specific verb and resource ("Obtient les métadonnées d'une pièce jointe"), and the word "métadonnées" implicitly distinguishes it from download_attachment and list_attachments. It does not explicitly name or contrast with any sibling, so it falls short of 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 guidance, no prerequisites, and no mention of alternatives such as list_attachments or download_attachment. The agent must infer from the name alone that this is the call for metadata rather than content.

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