Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_test_webhook

Sends a one-shot sample webhook delivery using the same payload shape, headers, and signature as a real event to test endpoint handling without retries or auto-disabling.

Instructions

Sends a sample delivery to your endpoint, instantly: the same shape, headers and signature as a real fire. One-shot: a failed test never retries and never auto-disables the webhook. 400 for an in-app webhook (nothing external to send to).

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>"
    },
    "name": "tickerbot_test_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhookYesWebhook id.

Output Schema

NameRequiredDescriptionDefault
idYesThe delivery id (`dlv_…`). Your endpoint receives it in `X-Tickerbot-Delivery-Id` (a resend sends the original's).
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`.
statusYesWhere the delivery stands. One of: `pending`, `delivered`, `permanent_failure`.
attemptYesAttempts made so far.
channelYesWhere it went. One of: `webhook`, `discord`, `in_app`, `mobile_push`.
deliveredYesWhether your endpoint accepted the test (2xx within the timeout).
created_atYesWhen it was queued (epoch seconds).
elapsed_msYesRound-trip time of the test.
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_ofYesOn a resend: the original delivery's id; `null` otherwise.
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. Changed4 schema fields changedv0.4.1
    • removedInput schema / properties / id
      Removed value: -{
      -  "description": "Webhook id.",
      -  "type": "string"
      -}
    • addedInput schema / properties / webhook
      Added value: +{
      +  "description": "Webhook id.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id"
      -]New value: +[
      +  "webhook"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "_advisories": {
      +      "description": "Present 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).",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "as_of": {
      +      "description": "Server time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "attempt": {
      +      "description": "Attempts made so far."
      +    },
      +    "body_string": {
      +      "description": "The exact JSON body, as sent."
      +    },
      +    "channel": {
      +      "description": "Where it went. One of: `webhook`, `discord`, `in_app`, `mobile_push`."
      +    },
      +    "created_at": {
      +      "description": "When it was queued (epoch seconds)."
      +    },
      +    "delivered": {
      +      "description": "Whether your endpoint accepted the test (2xx within the timeout)."
      +    },
      +    "delivered_at": {
      +      "description": "When your endpoint accepted it (epoch seconds); `null` until then."
      +    },
      +    "elapsed_ms": {
      +      "description": "Round-trip time of the test."
      +    },
      +    "event": {
      +      "description": "What fired. One of: `webhook.fired`, `events.fired`, `news.fired`."
      +    },
      +    "expires_at": {
      +      "description": "When it leaves the 90-day delivery history (epoch seconds); `null` on rows older than the field."
      +    },
      +    "id": {
      +      "description": "The delivery id (`dlv_…`). Your endpoint receives it in `X-Tickerbot-Delivery-Id` (a resend sends the original's)."
      +    },
      +    "last_error": {
      +      "description": "Why 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."
      +    },
      +    "last_status_code": {
      +      "description": "The 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."
      +    },
      +    "next_attempt_at": {
      +      "description": "When the next attempt is due, while `pending` (epoch seconds); `null` on a failed test fire, which is never retried."
      +    },
      +    "redelivery_of": {
      +      "description": "On a resend: the original delivery's id; `null` otherwise."
      +    },
      +    "status": {
      +      "description": "Where the delivery stands. One of: `pending`, `delivered`, `permanent_failure`."
      +    },
      +    "target_url": {
      +      "description": "The HTTPS endpoint it was sent to; `null` on every channel except `webhook`."
      +    },
      +    "test": {
      +      "description": "`true` on a test fire."
      +    },
      +    "webhook_id": {
      +      "description": "The webhook it belongs to."
      +    }
      +  },
      +  "required": [
      +    "as_of",
      +    "id",
      +    "webhook_id",
      +    "event",
      +    "status",
      +    "attempt",
      +    "last_status_code",
      +    "last_error",
      +    "channel",
      +    "target_url",
      +    "body_string",
      +    "created_at",
      +    "delivered_at",
      +    "next_attempt_at",
      +    "expires_at",
      +    "redelivery_of",
      +    "test",
      +    "delivered",
      +    "elapsed_ms"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses non-idempotent retry behavior ('a failed test never retries'), the absence of side effects on webhook state ('never auto-disables'), and the error condition (400 for in-app webhooks). It does not say whether the test is recorded as a visible delivery that can later be listed or redelivered, which is the main remaining unknown for a fire-and-send operation.

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 clauses, front-loaded with the action and payload equivalence, then the retry/state semantics, then the error case. No filler, and each sentence carries distinct information.

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?

Return values are covered by the output schema, so the description need not explain them. It is nearly complete for a one-parameter action tool; only the question of whether a test delivery enters the delivery log (relevant to the sibling list/redeliver tools) is left open.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter is already described as 'Webhook id.', so the baseline would be 3. The description adds real constraint beyond the schema by clarifying that the referenced webhook must target an external endpoint, since in-app webhooks return 400.

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?

Names a concrete action (sends a sample delivery) on a concrete resource (the webhook endpoint) and pins down what makes it distinct: 'the same shape, headers and signature as a real fire.' It stops short of naming the obvious sibling (tickerbot_redeliver_webhook_delivery), so the agent must infer the test-vs-real-redelivery boundary from wording alone.

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?

Usage is implied rather than stated: an agent can infer this is the pre-flight validation call before relying on a webhook. The '400 for an in-app webhook' line is a genuine when-not-to-use signal, but there is no explicit guidance on sequencing (e.g., test before enable) or on choosing this over redelivering a real delivery.

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