Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Redeliver webhook delivery

redeliver_webhook_delivery
Destructive

Resend a finished webhook delivery as a new delivery with its own ID and retry ladder, leaving the original untouched. Refuses deliveries that are still pending.

Instructions

Send a finished webhook delivery again. The stored payload goes out as a NEW delivery with its own id and its own retry ladder; the original row is left untouched and the new one records replayOf. A delivery that is still pending is refused.

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": {
      "deliveryId": "<deliveryId>"
    },
    "name": "redeliver_webhook_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
deliveryIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=true; the description goes well beyond that by explaining that a brand-new delivery is created with its own id and retry ladder, that the original row is untouched, and that the new row records replayOf. That is the key behavioral distinction an agent needs before invoking a mutation. It omits auth/permission requirements and rate-limit behavior, keeping it off 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?

Three short sentences, front-loaded with the action, then consequences, then the failure condition. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a destructive mutation, the description does the important work: it explains side effects, idempotency semantics (new row, replayOf link), and the pending-refusal rule. Missing only return-value expectations and how to source the deliveryId.

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, deliveryId, with 0% schema description coverage, so the description must carry the meaning. It implies the id must refer to a finished delivery and that pending ones are rejected, but it never says what form the id takes or how to obtain it, leaving a real gap for a 1-param tool.

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

Purpose5/5

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

States a specific verb and resource ('Send a finished webhook delivery again') plus the exact scope restriction ('finished'), so an agent can immediately tell this is a replay operation rather than a create or list call.

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?

Gives an explicit when-not condition: a delivery that is still pending is refused, which prevents a predictable error. It does not point at a sibling for discovering the delivery id (e.g. list_webhook_deliveries), so the routing guidance stops just short of complete.

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

Deploy Server

Other Tools