Skip to main content
Glama

Replay Webhook Delivery

replay_webhook_delivery

Retry a failed or cancelled webhook delivery after fixing the endpoint. Preserves the event ID so consumers can deduplicate. Active endpoints and current host authority are rechecked at delivery. Requires a write key.

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": {
      "event_id": "<event_id>",
      "delivery_id": "<delivery_id>"
    },
    "name": "replay_webhook_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes
delivery_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations declare non-read-only, non-idempotent, non-destructive, but say nothing about side effects, so the description carries the load and does it well: it discloses that the event ID is preserved for consumer deduplication, that endpoint activity and host authority are revalidated at delivery time, and that a write key is required. It omits what the call returns or how a failed replay is reported, which keeps it from a 5.

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?

Four short sentences, front-loaded with the action and its precondition, with the deduplication and validation guarantees following in descending priority. Every sentence adds information that is not already in the schema or annotations.

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?

For a two-parameter operation with no output schema, the description covers authorization, side effects, and delivery-time validation, which is solid. The remaining gap is the delivery_id's identity and provenance, plus the outcome of a replay attempt, which are documented nowhere in the definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the two required parameters. It mentions the event ID only obliquely ('Preserves the event ID'), and says nothing at all about what delivery_id is or how to obtain it, despite the schema enforcing a 64-character hex pattern that an agent cannot interpret from the schema alone.

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 opens with a specific verb and resource ('Retry a failed or cancelled webhook delivery') and scopes the eligible states, so an agent immediately knows this re-sends an existing delivery rather than creating a new webhook. It does not name or contrast a sibling tool, but no listed sibling performs the same replay action, so the risk of confusion is low.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the triggering condition ('failed or cancelled') and the precondition ('after fixing the endpoint'), which is exactly the decision context an agent needs before retrying. It stops short of explicit when-not guidance, such as what to do if the endpoint is still broken or how this differs from creating a fresh 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.