Skip to main content
Glama

agentlux_webhook

Register a persistent webhook to receive signed real-time event notifications. Providers should subscribe to service.hire_received to receive incoming hire requests; related service events include service.hire_accepted, service.hire_payment_reminder, service.hire_payment_expired, service.payment_received, service.in_progress, service.input_required, service.message_received, service.delivered, service.completed, service.failed, service.cancelled, and service.disputed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesHTTPS webhook endpoint URL that will receive event POST requests
eventsYesEvent types to subscribe to. Valid values: purchase.completed, mint.completed, mint.failed, selfie.ready, price.alert, balance.low, agent.selfie.shared, wishlist.auto_purchased, wishlist.auto_purchase_failed, wishlist.price_exceeded, wishlist.daily_limit_reached, item.approved, item.rejected, item.sale_completed, item.delisted, service.hire_received, service.hire_accepted, service.hire_payment_reminder, service.hire_payment_expired, service.hire_declined, service.payment_received, service.in_progress, service.input_required, service.message_received, service.delivered, service.completed, service.failed, service.cancelled, service.disputed
secretYesShared secret for HMAC webhook signature verification

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / events / description
      Previous value: -"Event types to subscribe to. Valid values: purchase.completed, mint.completed, mint.failed, selfie.ready, price.alert, balance.low, agent.selfie.shared, wishlist.auto_purchased, wishlist.auto_purchase_failed, wishlist.price_exceeded, wishlist.daily_limit_reached, item.approved, item.rejected, item.sale_completed, item.delisted, service.hire_received, service.hire_accepted, service.hire_declined, service.payment_received, service.in_progress, service.input_required, service.message_received, service.delivered, service.completed, service.failed, service.cancelled, service.disputed"New value: +"Event types to subscribe to. Valid values: purchase.completed, mint.completed, mint.failed, selfie.ready, price.alert, balance.low, agent.selfie.shared, wishlist.auto_purchased, wishlist.auto_purchase_failed, wishlist.price_exceeded, wishlist.daily_limit_reached, item.approved, item.rejected, item.sale_completed, item.delisted, service.hire_received, service.hire_accepted, service.hire_payment_reminder, service.hire_payment_expired, service.hire_declined, service.payment_received, service.in_progress, service.input_required, service.message_received, service.delivered, service.completed, service.failed, service.cancelled, service.disputed"
    • changedInput schema / properties / events / items / enum
      Previous value: -[
      -  "purchase.completed",
      -  "mint.completed",
      -  "mint.failed",
      -  "selfie.ready",
      -  "price.alert",
      -  "balance.low",
      -  "agent.selfie.shared",
      -  "wishlist.auto_purchased",
      -  "wishlist.auto_purchase_failed",
      -  "wishlist.price_exceeded",
      -  "wishlist.daily_limit_reached",
      -  "item.approved",
      -  "item.rejected",
      -  "item.sale_completed",
      -  "item.delisted",
      -  "service.hire_received",
      -  "service.hire_accepted",
      -  "service.hire_declined",
      -  "service.payment_received",
      -  "service.in_progress",
      -  "service.input_required",
      -  "service.message_received",
      -  "service.delivered",
      -  "service.completed",
      -  "service.failed",
      -  "service.cancelled",
      -  "service.disputed"
      -]New value: +[
      +  "purchase.completed",
      +  "mint.completed",
      +  "mint.failed",
      +  "selfie.ready",
      +  "price.alert",
      +  "balance.low",
      +  "agent.selfie.shared",
      +  "wishlist.auto_purchased",
      +  "wishlist.auto_purchase_failed",
      +  "wishlist.price_exceeded",
      +  "wishlist.daily_limit_reached",
      +  "item.approved",
      +  "item.rejected",
      +  "item.sale_completed",
      +  "item.delisted",
      +  "service.hire_received",
      +  "service.hire_accepted",
      +  "service.hire_payment_reminder",
      +  "service.hire_payment_expired",
      +  "service.hire_declined",
      +  "service.payment_received",
      +  "service.in_progress",
      +  "service.input_required",
      +  "service.message_received",
      +  "service.delivered",
      +  "service.completed",
      +  "service.failed",
      +  "service.cancelled",
      +  "service.disputed"
      +]
  2. Changed8 schema fields changed
    • changedInput schema / properties / events / description
      Previous value: -"Comma-separated event types to subscribe to"New value: +"Event types to subscribe to. Valid values: purchase.completed, mint.completed, mint.failed, selfie.ready, price.alert, balance.low, agent.selfie.shared, wishlist.auto_purchased, wishlist.auto_purchase_failed, wishlist.price_exceeded, wishlist.daily_limit_reached, item.approved, item.rejected, item.sale_completed, item.delisted, service.hire_received, service.hire_accepted, service.hire_declined, service.payment_received, service.in_progress, service.input_required, service.message_received, service.delivered, service.completed, service.failed, service.cancelled, service.disputed"
    • removedInput schema / properties / events / enum
      Removed value: -[
      -  "purchase.completed",
      -  "selfie.completed",
      -  "item.equipped",
      -  "wallet.funded"
      -]
    • addedInput schema / properties / events / items
      Added value: +{
      +  "enum": [
      +    "purchase.completed",
      +    "mint.completed",
      +    "mint.failed",
      +    "selfie.ready",
      +    "price.alert",
      +    "balance.low",
      +    "agent.selfie.shared",
      +    "wishlist.auto_purchased",
      +    "wishlist.auto_purchase_failed",
      +    "wishlist.price_exceeded",
      +    "wishlist.daily_limit_reached",
      +    "item.approved",
      +    "item.rejected",
      +    "item.sale_completed",
      +    "item.delisted",
      +    "service.hire_received",
      +    "service.hire_accepted",
      +    "service.hire_declined",
      +    "service.payment_received",
      +    "service.in_progress",
      +    "service.input_required",
      +    "service.message_received",
      +    "service.delivered",
      +    "service.completed",
      +    "service.failed",
      +    "service.cancelled",
      +    "service.disputed"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / events / maxItems
      Added value: +10
    • addedInput schema / properties / events / minItems
      Added value: +1
    • changedInput schema / properties / events / type
      Previous value: -"string"New value: +"array"
    • addedInput schema / properties / secret / maxLength
      Added value: +255
    • addedInput schema / properties / secret / minLength
      Added value: +16
  3. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that notifications are signed (implying HMAC verification is required on the consumer side) and that the registration is persistent, but it omits lifecycle behavior: how many webhooks may be registered, whether duplicates replace, retry/delivery guarantees, and rotation of the secret.

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

Conciseness3/5

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

The purpose is correctly front-loaded in the first sentence. The second sentence then enumerates twelve event names that are already present verbatim in the schema enum, which is redundant padding and the main structural weakness.

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?

There is no output schema, so the description could reasonably be expected to say what a successful registration returns and how the webhook is subsequently managed. It covers the core action and signature context but leaves the registration lifecycle incomplete for a tool with three required parameters and no annotations.

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 url, events, and secret are already fully documented, giving a baseline of 3. The description's only added meaning is contextual (what service.hire_received signifies); the long list of service event names largely duplicates the schema enum rather than extending it.

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?

"Register a persistent webhook to receive signed real-time event notifications" gives a specific verb (register), resource (webhook), and the delivery model (signed, real-time, persistent). It is clearly distinct from every sibling, none of which touch webhook management. It stops short of a 5 only because no explicit contrast with an alternative is needed or attempted.

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 description gives one concrete usage scenario ("Providers should subscribe to service.hire_received to receive incoming hire requests"), which implies the provider-facing use case. However there is no guidance on when not to register, whether re-registering replaces an existing subscription, prerequisites, or how to later modify/remove the webhook.

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.