Skip to main content
Glama

mcp-server

by io.github.tickerbot
OverviewDiscussionsAdmin

tickerbot_list_webhooks

Every webhook subscription on this account, newest first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size. Max 100.
cursorNoOpaque cursor from the previous response.
statusNoFilter by status: `active` or `disabled` — the only two states a webhook has (`disabled` covers both a user pause and the automatic disable after repeated delivery failures; `consecutive_failures`/`last_error` on each record say which). Omit for all.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofYesServer time this response was assembled (ISO 8601).
countYesRows in this page.
webhooksYesYour subscriptions, newest first, each with its `subscription_origin` and health fields. `signing_secret` is stripped — it is shown only on create.
next_cursorYesOpaque token for the next page; `null` on the last page. Pass it back as `cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "as_of": {
+      "description": "Server time this response was assembled (ISO 8601).",
+      "type": "string"
+    },
+    "count": {
+      "description": "Rows in this page.",
+      "type": "number"
+    },
+    "next_cursor": {
+      "description": "Opaque token for the next page; `null` on the last page. Pass it back as `cursor`.",
+      "type": "string"
+    },
+    "webhooks": {
+      "description": "Your subscriptions, newest first, each with its `subscription_origin` and health fields. `signing_secret` is stripped — it is shown only on create.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "as_of",
+    "count",
+    "next_cursor",
+    "webhooks"
+  ],
+  "type": "object"
+}
  2. Changed4 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque cursor."New value: +"Opaque cursor from the previous response."
    • addedInput schema / properties / limit / default
      Added value: +50
    • changedInput schema / properties / limit / description
      Previous value: -"Page size. Max 100. Default 50."New value: +"Page size. Max 100."
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status: `active` or `disabled`. Omit for all."New value: +"Filter by status: `active` or `disabled` — the only two states a webhook has (`disabled` covers both a user pause and the automatic disable after repeated delivery failures; `consecutive_failures`/`last_error` on each record say which). Omit for all."
  3. Changed2 schema fields changed
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status. Omit for all. (`pending_verification` = created but never successfully pinged.)"New value: +"Filter by status: `active` or `disabled`. Omit for all."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "active",
-  "pending_verification",
-  "disabled"
-]New value: +[
+  "active",
+  "disabled"
+]
  4. Changed2 schema fields changed
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status. Omit for all."New value: +"Filter by status. Omit for all. (`pending_verification` = created but never successfully pinged.)"
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "active",
-  "disabled"
-]New value: +[
+  "active",
+  "pending_verification",
+  "disabled"
+]
  5. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Page size."New value: +"Page size. Max 100. Default 50."
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Filter by status. Omit for all.",
+  "enum": [
+    "active",
+    "disabled"
+  ],
+  "type": "string"
+}
  6. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are present, so the description carries the behavioral disclosure burden. It does disclose two genuine behaviors: account-level scope and newest-first ordering. However, it says nothing about pagination mechanics (limit/cursor loop), the default page size of 50, or the read-only safety profile, and the nuanced 'disabled covers user pause and auto-disable' semantics live only inside the schema's status parameter, not the description.

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?

Seven words in a single sentence with zero filler. The resource, scope, and ordering are all front-loaded, and every word earns its place. This is appropriately concise rather than under-specified.

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 an output schema present and 100% parameter schema coverage, return values and inputs are already handled. The remaining gaps are routing guidance (when to choose this over list_webhook_deliveries or get_webhook) and explicit pagination-loop behavior, though 'Opaque cursor from the previous response' implies it. For a simple list endpoint this is adequate but leaves clear decision-making gaps.

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%, so the baseline of 3 applies. All three parameters (limit, cursor, status) are well-documented in the schema, including the opaque-cursor contract and the nuanced status enum semantics. The description itself adds nothing about parameters, but the schema fully compensates, so no deduction is warranted.

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 names the resource precisely ('webhook subscription'), its scope ('on this account'), and its ordering ('newest first'), which clearly communicates what the tool returns. It is implicitly distinguishable from siblings: get_webhook (singular), list_webhook_deliveries (delivery records, not subscriptions), and the create/delete/update/enable/test mutation tools. A small deduction because it is a noun phrase rather than an explicit verb phrase ('Returns every webhook…'), and it does not name the sibling distinctions.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. The description never mentions alternatives, exclusions, or the condition that would select this tool over get_webhook or list_webhook_deliveries. The appropriate use case is only implied by the tool name and the nouns in the description.

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

All mcp-server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources