Skip to main content
Glama
Grist MCP Server
by nic01asFr

Download Document Sqlite

download_document_sqlite

Download a Grist document as a SQLite database file by document ID, optionally as a template without user data or without modification history.

Instructions

Télécharge un document Grist au format SQLite.

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

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
templateNoSi True, télécharge comme modèle (sans données utilisateur)
nohistoryNoSi True, exclut l'historique des modifications

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 / nohistory / description
      Added value: +"Si True, exclut l'historique des modifications"
    • addedInput schema / properties / template / description
      Added value: +"Si True, télécharge comme modèle (sans données utilisateur)"
  2. First observedv0.1.0

TDQS

B3.2/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, and it discloses almost nothing: no mention of permissions needed, no note on what happens with attachments, history, or large documents, and no indication of whether the result is a file path, stream, or URL. The existence of an output schema excuses explaining return values, but not the operational caveats around a download/export 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 zero filler, so nothing needs trimming. Its brevity borders on under-specification, but no sentence is wasted or buried.

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 and fully documented parameters cover the mechanical side, so the definition is callable as written. It is still thin for an export tool with no annotations: an agent gets no information on permissions, side effects, or export caveats that would affect when it chooses this over the Excel sibling.

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 all three parameters (doc_id, template, nohistory) documented inline, so the schema already does the semantic work. The description adds no parameter meaning beyond that, which places it at the baseline for well-covered schemas.

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écharge un document Grist") plus the output format ("au format SQLite"), which implicitly distinguishes it from the sibling download_document_excel. It stops short of explicitly naming that alternative, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The stated format makes the usage context reasonably implied: use this when you want a SQLite dump rather than a CSV/Excel export. However, there is no explicit when-to-use guidance, no prerequisites, and no named sibling alternative to route against.

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