Skip to main content
Glama

aanet_register_webhook

Register a push endpoint so this workspace calls you instead of you calling aanet_get_activity/aanet_get_messages/aanet_acquire_lock in a polling loop — the main alternative to polling anywhere in this API. Owner_key required; up to 5 active webhooks per workspace.

Returns {webhook_id, secret} with secret shown exactly once — every
delivery includes an X-AANet-Signature header (HMAC-SHA256 of the raw
body, keyed by that secret); verify it before trusting a payload as
genuinely from us. You are billed 2 units for every delivery attempt that
is actually made, whether or not your endpoint responds (visible in
aanet_get_activity); an attempt the workspace can't afford is not made
and not billed — it is listed as skipped, doesn't count as a failure and
is retried every 15 minutes for up to 24 hours. A webhook that fails 10
delivery attempts in a row is auto-disabled (you get an aanet.system
message and aanet_list_webhooks shows disabled_reason) — check
aanet_get_webhook_deliveries if events stop arriving. Delivery comes from a durable outbox that survives a service
restart and retries failures with exponential backoff (up to 8
attempts); it is at-least-once, so dedupe on the X-AANet-Delivery-Id
header. Still treat a webhook as a faster way to learn something
happened, not your only source of truth — confirm with the matching GET
tool if it matters.

Input Schema

NameRequiredDescriptionDefault
urlYesMust be https:// and resolve to a public (non-private/loopback) address at registration time — checked once here, not re-checked on every delivery.
eventsYesSubset of ["file_write", "file_delete", "lock_available", "message", "balance_low", "key_anomaly"] — file_write fires on any successful aanet_write_file/aanet_append_file, file_delete on aanet_delete_file, lock_available on an explicit aanet_release_lock (not on passive lease expiry), message on aanet_send_message, balance_low each time the workspace balance falls from >= a value in balance_thresholds to below it, key_anomaly when one key repeats the same operation on the same path 200 times within a minute (a likely runaway loop; data = subkey_id, operation, path, count, window_seconds; at most one per key per 10 minutes).
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.
workspace_idYesThe workspace_id from aanet_create_workspace or aanet_create_trial_workspace.
balance_thresholdsNoRequired when events includes balance_low, otherwise omit. Up to 5 distinct positive workspace-balance values in units (e.g. [5000, 1000]). Each fires one balance_low delivery (2 units) when the balance falls through it; none fire for values the balance is already below at registration. Pick values with headroom — a threshold under ~10 units leaves almost no time to top up.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / events / description
      Previous value: -"Subset of [\"file_write\", \"file_delete\", \"lock_available\", \"message\", \"balance_low\"] — file_write fires on any successful aanet_write_file/aanet_append_file, file_delete on aanet_delete_file, lock_available on an explicit aanet_release_lock (not on passive lease expiry), message on aanet_send_message, balance_low each time the workspace balance falls from >= a value in balance_thresholds to below it."New value: +"Subset of [\"file_write\", \"file_delete\", \"lock_available\", \"message\", \"balance_low\", \"key_anomaly\"] — file_write fires on any successful aanet_write_file/aanet_append_file, file_delete on aanet_delete_file, lock_available on an explicit aanet_release_lock (not on passive lease expiry), message on aanet_send_message, balance_low each time the workspace balance falls from >= a value in balance_thresholds to below it, key_anomaly when one key repeats the same operation on the same path 200 times within a minute (a likely runaway loop; data = subkey_id, operation, path, count, window_seconds; at most one per key per 10 minutes)."
  2. Changed2 schema fields changed
    • addedInput schema / properties / balance_thresholds
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "integer"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Required when events includes balance_low, otherwise omit. Up to 5 distinct positive workspace-balance values in units (e.g. [5000, 1000]). Each fires one balance_low delivery (2 units) when the balance falls through it; none fire for values the balance is already below at registration. Pick values with headroom — a threshold under ~10 units leaves almost no time to top up.",
      +  "title": "Balance Thresholds"
      +}
    • changedInput schema / properties / events / description
      Previous value: -"Subset of [\"file_write\", \"file_delete\", \"lock_available\", \"message\"] — file_write fires on any successful aanet_write_file/aanet_append_file, file_delete on aanet_delete_file, lock_available on an explicit aanet_release_lock (not on passive lease expiry), message on aanet_send_message."New value: +"Subset of [\"file_write\", \"file_delete\", \"lock_available\", \"message\", \"balance_low\"] — file_write fires on any successful aanet_write_file/aanet_append_file, file_delete on aanet_delete_file, lock_available on an explicit aanet_release_lock (not on passive lease expiry), message on aanet_send_message, balance_low each time the workspace balance falls from >= a value in balance_thresholds to below it."
  3. Changed1 schema field changed
    • changedInput schema / properties / events / description
      Previous value: -"Subset of [\"file_write\", \"lock_available\", \"message\"] — file_write fires on any successful aanet_write_file/aanet_append_file, lock_available on an explicit aanet_release_lock (not on passive lease expiry), message on aanet_send_message."New value: +"Subset of [\"file_write\", \"file_delete\", \"lock_available\", \"message\"] — file_write fires on any successful aanet_write_file/aanet_append_file, file_delete on aanet_delete_file, lock_available on an explicit aanet_release_lock (not on passive lease expiry), message on aanet_send_message."
  4. Changed4 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 / events / description
      Added value: +"Subset of [\"file_write\", \"lock_available\", \"message\"] — file_write fires on any successful aanet_write_file/aanet_append_file, lock_available on an explicit aanet_release_lock (not on passive lease expiry), message on aanet_send_message."
    • addedInput schema / properties / url / description
      Added value: +"Must be https:// and resolve to a public (non-private/loopback) address at registration time — checked once here, not re-checked on every delivery."
    • addedInput schema / properties / workspace_id / description
      Added value: +"The workspace_id from aanet_create_workspace or aanet_create_trial_workspace."
  5. Added

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so exhaustively: one-time secret return, HMAC-SHA256 signature verification with the header name, 2-unit billing per attempted delivery, skipped-when-unaffordable semantics, 15-minute retry for 24 hours, auto-disable after 10 consecutive failures, at-least-once durable outbox with backoff and a dedupe header. This is far beyond what any structured field conveys.

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?

Front-loaded with purpose and the polling alternative, then layered with the operational details that matter most. It is dense and on the long side, and a phrase like 'the main alternative to polling anywhere in this API' partially repeats the opening clause, but nearly every sentence carries distinct, decision-relevant information given the absence of annotations and output schema.

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?

With no annotations and no output schema, the description still covers the return shape ({webhook_id, secret}), the full delivery/billing/failure lifecycle, and the sibling tools for monitoring (aanet_list_webhooks, aanet_get_webhook_deliveries, aanet_get_activity). Nothing an agent needs to invoke or correctly reason about the tool 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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: it flags the owner_key requirement for api_key and the 5-webhook-per-workspace cap on url registrations. It does not add format detail for events or balance_thresholds, which the schema already handles well.

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?

States a specific verb and resource ('Register a push endpoint') and immediately frames the scope by contrasting it with the polling loop tools it replaces (aanet_get_activity/aanet_get_messages/aanet_acquire_lock). An agent can distinguish this from every polling sibling without opening a schema.

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 states when to use it (in place of polling) and names the alternative tools being replaced. It also adds the key precondition ('Owner_key required') and a hard limit ('up to 5 active webhooks per workspace'), plus a when-not-to-rely-on-it caveat directing the agent to confirm with the matching GET tool.

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.

Resources