Skip to main content
Glama
Sign In
Lightning Wallet MCP

Lightning Wallet MCP

by lightningfaucet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_invoice

Generate a Lightning invoice to receive payment by specifying the amount in satoshis and an optional memo. Enables instant fund reception over the Lightning Network.

Instructions

Create a Lightning invoice to receive payment. Use get_invoice_status to check if paid.

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": "create_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoNoDescription/memo for the invoice
amount_satsYesAmount in satoshis to request

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.9

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It states creation but omits potential side effects, authorization needs, or return behavior. Adequate but minimal.

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?

Single sentence with a useful hint. Extremely concise, front-loaded, no extra words.

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?

With 2 params, no output schema, and no annotations, the description provides basic functionality and a follow-up tip. Missing details like return value (invoice string) but meets minimum needs.

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 coverage is 100% with clear descriptions for both params. The description adds no additional meaning beyond the schema.

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?

Clearly states 'Create a Lightning invoice to receive payment' – specific verb and resource. Distinguishes from sibling tools like get_invoice_status and decode_invoice.

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?

Explicitly suggests using get_invoice_status to check payment, but does not specify when to use this tool versus other payment-related siblings like pay_invoice or keysend. However, the purpose is implied.

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

Deploy Server

Other Tools