Skip to main content
Glama
Grist MCP Server
by nic01asFr

Force Reload Document

force_reload_document

Reloads a Grist document to resolve inconsistencies or synchronization issues. Provide the document ID to refresh its state from the server.

Instructions

Force le rechargement d'un document.

Utile en cas d'incohérences ou de problèmes de synchronisation.

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

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document à recharger

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document à recharger"
  2. First observedv0.1.0

TDQS

B3.4/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 burden. It says the reload is 'forced' but never states whether that is destructive, whether it requires elevated permissions, whether it invalidates other users' sessions, or whether it is synchronous. Only the symptom it addresses is disclosed.

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?

Two short sentences with no filler, and the action is stated first with the rationale second. It could be tightened further only by folding the use case into the same sentence.

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 explained, and the tool has only one required parameter. Still, for a state-mutating force operation with zero annotation coverage, the description leaves the safety and side-effect profile unaddressed.

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 the single doc_id parameter is documented in the schema itself. The description adds no meaning about the identifier's format or whether it comes from a workspace listing, 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 states a specific verb and resource: forcing the reload of a document. That is more precise than the title alone, which merely restates the name. It does not, however, differentiate the tool from neighbours such as modify_document, describe_document, or download_document_*.

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

Usage Guidelines4/5

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

The second sentence gives a clear trigger condition: use it when there are inconsistencies or synchronization problems. It gives no explicit exclusions and names no alternative tool, but the context for calling it is stated rather than implied.

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