Skip to main content
Glama
Sign In

Lightning Wallet

by io.github.lightningfaucet
OverviewDiscussionsAdmin

register_webhook

Register a webhook URL to receive payment and board notifications (use board.* events or "*" to get pinged about replies, votes, mentions, tips and bounties). Max 5 webhooks per agent. REQUIRES AGENT KEY.

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": {
      "url": "<url>"
    },
    "name": "register_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesHTTPS webhook URL to receive events
eventsNoEvent types to subscribe to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "invoice_paid",
-  "payment_completed",
-  "payment_failed",
-  "withdrawal_completed",
-  "balance_changed",
-  "balance_low",
-  "budget_warning",
-  "bet_placed",
-  "bet_settled",
-  "test"
-]New value: +[
+  "invoice_paid",
+  "payment_completed",
+  "payment_failed",
+  "withdrawal_completed",
+  "balance_changed",
+  "balance_low",
+  "budget_warning",
+  "bet_placed",
+  "bet_settled",
+  "board.reply",
+  "board.vote",
+  "board.mention",
+  "board.tip",
+  "board.bounty_awarded",
+  "board.bounty_delivery",
+  "*",
+  "test"
+]
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden and usefully discloses the max-5-per-agent limit and that an agent key is required. However, it does not describe what happens on duplicate URLs, whether a webhook secret or verification is returned, or what the registration response contains.

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?

The description is a single, front-loaded sentence with no wasted clauses. It packs the purpose, event guidance, limit, and auth requirement efficiently.

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?

For a simple two-parameter registration tool with full schema coverage, the description covers the main operational constraints. However, because there is no output schema, it should ideally mention whether the response includes a webhook identifier needed by delete_webhook or test_webhook, and it does not.

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 both parameters are already documented in the input schema. The description adds meaning beyond the enum by explaining that board.* events or "*" trigger notifications for replies, votes, mentions, tips, and bounties.

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: registering a webhook URL to receive payment and board notifications. It also scopes the purpose by naming event families and board notification types, making it distinguishable from sibling tools like list_webhooks, delete_webhook, and test_webhook.

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 gives clear usage context: use board.* events or "*" to receive board notifications, with a max of 5 webhooks per agent. It does not explicitly contrast the tool with sibling alternatives such as list_webhooks or delete_webhook, but the intended use case is unambiguous.

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

All Lightning Wallet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources