Skip to main content
Glama
Grist MCP Server
by nic01asFr

Clear Webhook Queue

clear_webhook_queue

Clears the webhook queue for a Grist document, helping resolve accumulated unsent notifications.

Instructions

Vide la file d'attente des webhooks pour un document.

Utile en cas d'accumulation de notifications non envoyées.

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

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document

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

TDQS

B3.3/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 and it falls short: it never says whether clearing is irreversible, whether the unsent notifications are discarded or retried, or what permissions are required. For a destructive-sounding mutation on queued notifications, these omissions are significant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and followed by the use case; there is no filler or redundant restatement of the title.

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 single parameter is covered. What remains missing is the destructive semantics and any recovery information, which matter for a queue-clearing tool with no annotations.

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% and the only parameter (doc_id) is documented in the schema as 'L'ID du document'. The description reinforces that scope is a single document but adds no format, validation, or edge-case detail beyond what the schema already states.

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 ('Vide la file d'attente des webhooks') plus the scope 'pour un document', so an agent can tell it acts on one document's queue rather than globally. It does not contrast itself with the sibling webhook tools (delete_webhook, modify_webhook), so sibling differentiation is left to inference.

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 en cas d'accumulation de notifications non envoyées' gives a concrete trigger condition for calling it, which is more than nothing. However, it offers no when-not guidance, no prerequisites, and no mention of alternatives such as inspecting the queue first or using delete_webhook.

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