Skip to main content
Glama

Replay event

replay_event
Destructive

Send an event again to one webhook endpoint (after fixing the receiver).

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": {
      "id": "<id>",
      "endpoint_id": "<endpoint_id>"
    },
    "name": "replay_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEvent id
endpoint_idYesThe webhook endpoint to send it to (we_...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / endpoint_id / description
      Added value: +"The webhook endpoint to send it to (we_...)"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true. The description reinforces intent ('send again', fix receiver first) but never spells out the consequence that each call delivers a real external webhook and that repeating the call produces duplicate deliveries with no rollback, which is the key risk an agent needs.

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 front-loaded sentence with no filler; the verb and the target are immediately visible. It is efficient but borders on under-specification for a destructive, non-idempotent operation.

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?

With only two fully-described parameters, rich annotations and no output schema, most of the burden is carried elsewhere. Still missing is what happens after the replay (does it return a delivery record? does it error if the endpoint is still broken?), which an agent needs before invoking a destructive tool.

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% — both 'id' and 'endpoint_id' are documented inline, including the 'we_...' prefix. The description adds nothing beyond that, so baseline 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?

States a specific verb+resource: re-send an existing event to a single webhook endpoint. The phrase 'one webhook endpoint' implicitly separates it from the bulk replay_failed_webhooks sibling, though it never names that sibling explicitly.

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?

The parenthetical '(after fixing the receiver)' implies the intended workflow — repair the endpoint first, then replay — but there is no explicit when-to-use vs. when-to-use-instead guidance against replay_failed_webhooks or test_webhook.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.