Skip to main content
Glama
Grist MCP Server
by nic01asFr

Delete Document History

delete_document_history

Deletes a Grist document's history while keeping a specified number of recent actions, helping reduce the size of large documents.

Instructions

Supprime l'historique d'un document, ne conservant que les dernières actions.

Utile pour réduire la taille des documents volumineux.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
keepNoNombre d'actions récentes à conserver (défaut: 1000)
doc_idYesL'ID du document

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"
    • addedInput schema / properties / keep / description
      Added value: +"Nombre d'actions récentes à conserver (défaut: 1000)"
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 does disclose the crucial non-obvious behavior that deletion is partial (recent actions are preserved), which is genuinely useful, but it omits irreversibility, required permissions, and what happens if the retained count exceeds existing history.

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; the destructive action is front-loaded and the rationale follows. It is lean and readable, though the second sentence is a justification rather than additional operational detail.

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 parameters are fully covered by the schema. Still, for a destructive, non-readonly mutation with zero annotations, the description should say more about irreversibility and safety to be complete.

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%, so both doc_id and keep are already documented with defaults, making 3 the baseline. The description's phrase "ne conservant que les dernières actions" loosely reinforces the keep parameter but adds no format, bounds, or edge-case meaning beyond the schema.

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?

States a specific verb and resource ("Supprime l'historique d'un document") and immediately qualifies the scope with "ne conservant que les dernières actions", which distinguishes it from a full document deletion. It does not explicitly contrast with delete_document or delete_grist_records, so an agent must infer the boundary.

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?

"Utile pour réduire la taille des documents volumineux" gives a use-case rationale, which is more than nothing. However, there is no when-not guidance, no mention that a full removal is handled by delete_document, and no prerequisites such as required permissions.

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