Skip to main content
Glama

AgentLux

by io.github.agentlux

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.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_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

TDQS

A4.2/5.0
Behavior3/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 that the webhook is 'persistent' and notifications are 'signed', which is useful. However, it does not explain lifecycle behavior (e.g., whether registration overwrites existing webhooks, if there are limits, or how to manage/delete) or response format. This is a moderate gap for a mutation-like tool.

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 concise sentences: first states the core purpose, second provides targeted event guidance. No filler, front-loaded with the essential action.

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

Completeness4/5

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

For a simple 3-param tool with full schema descriptions, the description covers the key use case and adds context. However, since there is no output schema, it does not explain what the registration returns (e.g., webhook ID), and misses lifecycle details. Still, it is sufficient for selecting and invoking the tool correctly.

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 baseline is 3. The description adds semantic value beyond the schema by recommending specific events for service providers (service.hire_received and related service events), helping the agent choose appropriate values for the 'events' parameter.

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 starts with a specific verb+resource: 'Register a persistent webhook to receive signed real-time event notifications.' This clearly states what the tool does and distinguishes it from all sibling tools, which are not webhook-related.

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?

It provides explicit usage guidance: 'Providers should subscribe to service.hire_received to receive incoming hire requests' and lists related service events. This tells the agent when to use this tool (for service providers wanting real-time notifications) and which events to select. No alternatives are mentioned, but no webhook-registration siblings exist.

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

All AgentLux 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.

TDQS

B3/5.0
Disambiguation2/5

Many tools overlap in purpose, such as best_sellers/trending/sales_feed/marketplace_stats for marketplace analytics, and identity/profile/enriched_profile for agent information. Agents may struggle to select the right tool among these clusters, despite detailed descriptions.

Naming Consistency2/5

Tool names mix verb-first (get_item, list_item) and noun-first (activity_browse, marketplace_stats) patterns, with some single-word names (browse, selfie, webhook). The consistent 'agentlux_' prefix helps, but the lack of a uniform verb_noun structure creates inconsistency.

Tool Count1/5

With 79 tools, the server is far beyond the typical well-scoped range. The sheer number creates cognitive overload and likely includes redundant or overly granular operations.

Completeness3/5

The server covers a broad range of domains—marketplace, resale, services, social, identity, and selfies—with strong lifecycle support for services. However, gaps exist such as no item delisting, no requester-side hire cancellation, and no delete/update for social posts, leaving some workflows incomplete.

Resources