Skip to main content
Glama
Sign In

Lightning Wallet

by io.github.lightningfaucet
OverviewDiscussionsAdmin

get_deposit_invoice

Create a Lightning invoice to fund your operator account. Pay this invoice to add sats to your balance.

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": {
      "amount_sats": "<amount_sats>"
    },
    "name": "get_deposit_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_satsYesAmount in satoshis to deposit (minimum 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / amount_sats / description
      Previous value: -"Amount in satoshis to deposit"New value: +"Amount in satoshis to deposit (minimum 10)"
    • changedInput schema / properties / amount_sats / minimum
      Previous value: -100New value: +10
  2. First observed

TDQS

A3.5/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 full burden. It does usefully disclose the funding flow and where the sats land (operator account balance), but omits key behavior: whether each call mints a new invoice, whether invoices expire or are single-use, and whether the operation has side effects despite the 'get_' name. That name/verb mismatch ('get' vs 'Create') could mislead an agent into expecting a retrieval.

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 short sentences, front-loaded with the action and followed by the next step. Every sentence earns its place with no filler.

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 single-parameter tool with no output schema and no annotations, the description should explain what is returned (e.g. a bolt11 invoice string) and any expiry behavior. It covers the purpose and follow-up action but leaves the return value and repeat-call semantics unexplained.

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% and the single parameter includes its own description plus a minimum of 10. The description adds nothing about the amount parameter, so the baseline of 3 applies.

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?

States a specific verb and resource: 'Create a Lightning invoice to fund your operator account.' An agent immediately knows this generates a funding invoice rather than paying one. It stops short of differentiating from the sibling create_invoice, which does something similar, so the caller cannot tell the two apart from the text alone.

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 second sentence, 'Pay this invoice to add sats to your balance,' gives implied guidance by describing the follow-up step. There is no explicit when-to-use versus create_invoice or fund_agent, and no exclusion or prerequisite information, so usage must be inferred.

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