Skip to main content
Glama

AANet

by space.aanet
OverviewDiscussionsAdmin

aanet_get_webhook_deliveries

Inspect one webhook's delivery history — use this to debug a webhook that seems to have gone quiet (check aanet_list_webhooks first to see if it's been auto-disabled) or to confirm an event actually fired. Owner_key required. Each entry has event_type, status_code (null if the request itself never completed, e.g. timeout or DNS failure), and success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum delivery records to return, newest first, up to 200.
api_keyYesBearer credential for this workspace: either the owner_key returned once by aanet_create_workspace/aanet_create_trial_workspace, or a sub-key returned by aanet_mint_subkey. Sent under the hood as `Authorization: Bearer <api_key>`. Owner-only tools reject a sub-key with a 403.
webhook_idYesThe webhook_id from aanet_register_webhook or aanet_list_webhooks.
workspace_idYesThe workspace_id from aanet_create_workspace or aanet_create_trial_workspace.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / api_key / description
      Added value: +"Bearer credential for this workspace: either the owner_key returned once by aanet_create_workspace/aanet_create_trial_workspace, or a sub-key returned by aanet_mint_subkey. Sent under the hood as `Authorization: Bearer <api_key>`. Owner-only tools reject a sub-key with a 403."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum delivery records to return, newest first, up to 200."
    • addedInput schema / properties / limit / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / webhook_id / description
      Added value: +"The webhook_id from aanet_register_webhook or aanet_list_webhooks."
    • addedInput schema / properties / workspace_id / description
      Added value: +"The workspace_id from aanet_create_workspace or aanet_create_trial_workspace."
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses the output fields (event_type, status_code, success) and explains the special case where status_code is null (timeout/DNS failure). It also clarifies the api_key requirement (Owner_key). It does not explicitly state 'read-only' but 'inspect' implies it; this is adequate but could be more explicit.

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?

Two sentences, front-loaded with the primary purpose and use case. Every clause earns its place: the parenthetical about checking list_webhooks is essential routing guidance, and the output field breakdown is concise. No redundancy or fluff.

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?

Given that the tool has an output schema, all parameters are fully described, and the description covers use cases, prerequisites, and output semantics, everything an agent needs to select and invoke the tool correctly is present. The tool is a simple read-style operation; no additional context is missing.

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 100%, so the baseline is 3. The description adds value by specifying that the api_key must be the Owner_key (not a sub-key), which is a meaningful clarification beyond the generic api_key parameter description. It also ties the output structure to the purpose but does not elaborate per-param usage beyond that.

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 states a specific verb and resource ('Inspect one webhook's delivery history') and clarifies its purpose by contrasting with a sibling tool ('check aanet_list_webhooks first'). It also specifies the use case 'confirm an event actually fired', making the tool's scope unambiguous.

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

Usage Guidelines5/5

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

Explicitly tells when to use it: to debug a quiet webhook or confirm an event fired, and even suggests a prerequisite step (checking aanet_list_webhooks for auto-disabled status). It also notes that Owner_key is required, which is a clear precondition.

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

All AANet toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources