Skip to main content
Glama
Sign In
Thesma MCP Server

Thesma MCP Server

Official
by thesma-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_webhook_deliveries

List webhook delivery attempts for a subscription to debug issues. Each entry shows event type, status, attempt count, and timestamps. Use page parameter for next batch.

Instructions

Show delivery attempts for a webhook subscription. Useful for debugging — each row shows event type, status, attempt count, and queued/completed timestamps. Pagination is offset-based: pass page=2 for the next batch. limit (per page) is capped at 50 server-side.

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": {
      "subscription_id": "<subscription_id>"
    },
    "name": "list_webhook_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
subscription_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses offset-based pagination ('pass page=2 for the next batch'), the server-side cap on limit (50), and what each row contains (event type, status, attempt count, timestamps). This goes beyond a simple listing and gives useful behavioral details.

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 concise sentences, each earning its place: purpose + use case, output row fields, and pagination behavior. No fluff or redundancy.

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

Completeness5/5

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

The description fully covers the tool's purpose, return contents, and pagination mechanics. With an output schema available for exact return format, the description is sufficient for an agent to select and invoke the tool correctly. It also addresses the key nuance of limit capping.

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 description coverage is 0%, so the description must compensate. It explains 'page' semantics explicitly ('pass page=2 for the next batch') and clarifies that 'limit' is capped at 50. 'subscription_id' is self-evident from the tool name and the phrase 'for a webhook subscription'. This is adequate compensation for the missing schema descriptions.

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 clearly states 'Show delivery attempts for a webhook subscription' with a specific verb and resource. It distinguishes itself from sibling tools like list_webhooks (which lists subscriptions) and replay_webhook_delivery (which replays deliveries).

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?

The description says 'Useful for debugging' which provides clear context on when to use this tool. It does not mention explicit alternatives or exclusions, but the use case is well implied by the debugging note and the row content described.

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