Skip to main content
Glama
Grist MCP Server
by nic01asFr

Move Document

move_document

Moves a Grist document to a specified target workspace by document ID, enabling reorganization of documents across workspaces.

Instructions

Déplace un document vers un autre espace de travail.

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>",
      "target_workspace_id": "<target_workspace_id>"
    },
    "name": "move_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document à déplacer
target_workspace_idYesL'ID de l'espace de travail de destination

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.2
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document à déplacer"
    • addedInput schema / properties / target_workspace_id / description
      Added value: +"L'ID de l'espace de travail de destination"
  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 a move happens. It says nothing about required permissions on the source or target workspace, what happens to sharing/access entries when the document moves, whether the document ID or existing links survive, or whether the operation is reversible.

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 grammatical sentence with the action and destination front-loaded and no filler. Its brevity is partly due to omission rather than disciplined editing, but there is no structural problem to penalize.

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?

For a destructive-ish mutation with zero annotations, the description should at minimum flag permission and access-side-effect concerns; an output schema exists, so return values need not be explained. With both parameters documented in the schema, the remaining gap is entirely behavioral, and the description does not close it.

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 coverage is 100%, with both doc_id and target_workspace_id described in the schema itself, so the baseline is 3. The description's "vers un autre espace de travail" merely restates target_workspace_id and adds no format or constraint detail.

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 names a specific verb and resource ("Déplace un document") and its destination scope ("vers un autre espace de travail"), which is enough to separate it from sibling mutations like create_document or delete_document. It stops short of any explicit sibling differentiation, so it lands just below the top.

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 instead of modify_document, delete_document, or any other sibling, and no prerequisites are stated. The agent must infer the entire usage context from the one-line purpose.

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