Skip to main content
Glama
Grist MCP Server
by nic01asFr

Upload Attachment

upload_attachment

Upload a base64-encoded file as an attachment to a specified Grist document, with optional MIME type setting for correct file handling.

Instructions

Téléverse une pièce jointe dans 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>",
      "filename": "<filename>",
      "content_base64": "<content_base64>"
    },
    "name": "upload_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
filenameYesNom du fichier
content_typeNoType MIME du fichierapplication/octet-stream
content_base64YesContenu du fichier encodé en base64

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.2
    • addedInput schema / properties / content_base64 / description
      Added value: +"Contenu du fichier encodé en base64"
    • addedInput schema / properties / content_type / description
      Added value: +"Type MIME du fichier"
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document"
    • addedInput schema / properties / filename / description
      Added value: +"Nom du fichier"
  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 provided, so the description carries the full behavioral burden, yet it only restates that an upload occurs. It says nothing about mutation semantics, required permissions, size/type limits, overwrite behavior, or what the returned attachment reference looks like — meaningful gaps for a write operation.

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. Its brevity is appropriate structurally, though the same brevity is what leaves behavioral gaps noted elsewhere.

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?

An output schema exists, so return values need not be explained, but for a mutation tool with zero annotations the description should cover permissions, size limits, and failure modes. None of that is present, and it is also written in French while the tool name and siblings are English, which adds a small comprehension cost.

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% and each of the four parameters is documented in the schema, including the base64 encoding of content_base64 and the MIME default for content_type. The description adds no extra meaning such as encoding constraints or filename sanitization, 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?

The description gives a specific verb and resource ('Téléverse une pièce jointe') plus the target context ('dans un document Grist'), which cleanly separates it from download_attachment, list_attachments and get_attachment_info. It stops short of explicitly naming a sibling or stating scope limits, so it is clear but not maximally differentiated.

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 use this tool versus the other attachment tools, and no prerequisites such as needing an existing attachment column, document write permission, or a maximum payload size. The agent must infer the whole usage context 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.