Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_redeliver_webhook_delivery

Resends a past webhook delivery with its original body to the webhook's current target; use a delivery ID from the delivery list and ensure the webhook is active (test fires excluded).

Instructions

Resends a past delivery, with the exact body it carried, to the webhook's current target. The webhook must be active (409 otherwise); take delivery ids from tickerbot_list_webhook_deliveries. Test fires cannot be resent.

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": {
      "webhook": "<webhook>",
      "delivery": "<delivery>"
    },
    "name": "tickerbot_redeliver_webhook_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhookYesWebhook id.
deliveryYesThe delivery to resend, from `GET /v2/webhooks/{webhook}/deliveries`.

Output Schema

NameRequiredDescriptionDefault
idYesThe new delivery's id (`dlv_…`), listed on the deliveries route with its outcome.
testYes`true` on a test fire.
as_ofYesServer time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).
eventYesWhat fired. One of: `webhook.fired`, `events.fired`, `news.fired`.
statusYes`pending`: queued, sent on the next delivery pass with the full retry ladder. One of: `pending`, `delivered`, `permanent_failure`.
attemptYesAttempts made so far.
channelYesWhere it went. One of: `webhook`, `discord`, `in_app`, `mobile_push`.
created_atYesWhen the resend was queued (epoch seconds).
expires_atYesWhen it leaves the 90-day delivery history (epoch seconds); `null` on rows older than the field.
last_errorYesWhy the last attempt failed when your endpoint could not be reached (a network error or the 10-second timeout); `null` when it answered (see `last_status_code`) or on success. Discord and mobile-push deliveries also describe a rejected request here.
target_urlYesThe HTTPS endpoint it was sent to; `null` on every channel except `webhook`.
webhook_idYesThe webhook it belongs to.
_advisoriesNoPresent only when the response carried a warning: `deprecated` (since, sunset_on, successor, warning; on a deprecated tool, successor names the tool to call), `rate_limit` (warning, retry_after_seconds, limit, remaining, reset_epoch_s) or `monthly_quota` (warning, limit, remaining, reset_epoch_s).
body_stringYesThe exact JSON body, as sent.
delivered_atYesWhen your endpoint accepted it (epoch seconds); `null` until then.
redelivery_ofYesThe original delivery's id, even when you resend a resend. The original's id is the `X-Tickerbot-Delivery-Id` your endpoint receives.
next_attempt_atYesWhen the next attempt is due, while `pending` (epoch seconds); `null` on a failed test fire, which is never retried.
last_status_codeYesThe HTTP status your endpoint returned on the last attempt; `null` when it could not be reached, before the first attempt, and on in-app deliveries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that the original body is replayed verbatim, that delivery goes to the webhook's current target rather than the original endpoint, and that an inactive webhook yields a 409. It does not address whether a new delivery record is created, whether the failure/auto-disable state is affected, or whether signature headers are recomputed for the replayed body — meaningful gaps for a redelivery tool.

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 what the tool does, then prerequisites and exclusion. No filler and nothing repeated from the schema or annotations.

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?

An output schema exists, so return values need no explanation, and the description covers the key preconditions and the mutation's core semantics. The remaining gap is header/signature handling on replay and any side effects on the webhook's delivery history — details an agent invoking a webhook redelivery would want, and which no structured field supplies.

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%, so both `webhook` and `delivery` are already documented, and the schema itself points to the deliveries endpoint. The description adds only the eligibility nuance that test fires cannot be supplied as a delivery id, which is marginal added meaning; baseline 3 is appropriate.

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?

The description names a specific verb (resends) and a precise resource (a past webhook delivery), plus the two distinguishing details that separate it from siblings: the exact original body goes to the webhook's current target, not the original one. An agent can distinguish this from tickerbot_test_webhook or tickerbot_list_webhook_deliveries without opening a schema.

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 gives a clear precondition (the webhook must be active), routes the agent to tickerbot_list_webhook_deliveries as the source of valid delivery ids, and states an exclusion (test fires cannot be resent). It stops short of explicitly saying 'use tickerbot_test_webhook instead for test fires', so the alternative routing is implied rather than spelled out.

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