Skip to main content
Glama
Grist MCP Server
by nic01asFr

Delete Document

delete_document

Deletes a Grist document by its document ID, enabling cleanup of unused or obsolete documents from your workspace.

Instructions

Supprime un document.

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

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document à supprimer

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 à supprimer"
  2. First observedv0.1.0

TDQS

C2.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 of behavioral disclosure, yet it says nothing about irreversibility, whether the document goes to a trash, required permissions, or the consequence of deleting an already-deleted document. The only behavioral signal is the verb 'supprime', which is already implied by the name.

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?

The description is a single short sentence with no wasted words, but it is under-specified rather than well-structured. Brevity here reflects a missing explanation rather than disciplined editing.

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 and the single required parameter is documented, so the mechanical minimum is met. However, for a destructive operation with no annotations, the definition omits confirmation behavior, reversibility, and failure modes that an agent needs before invoking 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?

There is a single parameter, doc_id, whose schema description ('L'ID du document à supprimer') provides full coverage at 100%. The description adds no meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Supprime un document' merely restates the tool name and title (delete_document / Delete Document) with no additional specificity. It does not clarify scope, such as whether the deletion is permanent or which document type is targeted, nor does it distinguish it from siblings like delete_document_history or delete_grist_records.

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 alternatives such as delete_document_history or force_reload_document. No prerequisites, confirmation steps, or exclusions are stated, leaving the agent to infer usage entirely.

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