Skip to main content
Glama

RenewRoster

Webhook delivery log

list_webhook_deliveries
Read-onlyIdempotent

Recent deliveries for one webhook with status, attempts and HTTP code.

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

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that results are 'recent' and include status, attempts, and HTTP code, but it does not clarify recency window, ordering, pagination, or default limits. With annotations carrying the core behavioral burden, this is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted words. It is appropriately sized for a simple list tool, though the compressed phrasing 'with status, attempts and HTTP code' could be slightly clearer about return values.

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 no output schema and 0% schema description coverage, the description helps by naming returned fields (status, attempts, HTTP code). However, it omits critical details for a list operation: what 'recent' means, how limit controls results, ordering, and pagination behavior. It is minimally complete but leaves meaningful gaps.

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

Parameters2/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 for both parameters. It implies that 'id' refers to one webhook and that results are 'recent', but it never mentions the 'limit' parameter or explains its allowed range (1-200). The added meaning is partial and leaves the limit parameter undocumented.

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 uses a clear verb-resource pairing: listing recent deliveries for a webhook, and it specifies the returned fields (status, attempts, HTTP code). It distinguishes itself from list_webhooks by scoping to deliveries of a single webhook, though it does not explicitly name or rule out sibling tools.

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?

The phrase 'for one webhook' implies the tool is used when inspecting a specific webhook's delivery history, giving minimal contextual guidance. However, it does not state when to prefer it over alternatives like list_webhooks or get_asset_history, nor does it mention exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.