Skip to main content
Glama
Sharmaz

Phoenixd MCP Server

by Sharmaz

create-invoice

Generate a Bolt11 Lightning invoice with a custom amount, description, expiry, and webhook callback to receive Bitcoin payments.

Instructions

Create a bolt11 invoice with a specified amount and description

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoThe description of the invoice (max. 128 characters). Either description or descriptionHash must be provided.
descriptionHashNoSHA256 hash of the description. Use instead of description.
amountSatNoThe amount requested by the invoice, in satoshi. If not set, the invoice can be paid by any amount.
expirySecondsNoThe invoice expiry in seconds, by default 3600 (1 hour).
externalIdNoA custom identifier. Use that to link the invoice to an external system.
webhookUrlNoA webhook url that will be notified when this specific payment has been received.
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only implies mutation (create) without specifying persistence, authentication needs, rate limits, or return value.

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

Conciseness4/5

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

The description is a single, efficient sentence with no extraneous information. It is clear and front-loaded, but could be slightly expanded for completeness.

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

Completeness2/5

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

Given no output schema and no annotations, the description should explain what the tool returns and any side effects. It lacks this context, making it incomplete for an AI agent.

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?

The input schema has 100% coverage with descriptions for all 6 parameters. The tool description adds no additional value beyond the schema, meeting the baseline for high schema coverage.

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?

The description clearly states the tool creates a bolt11 invoice with amount and description. It is distinct from sibling tools like pay-invoice or decode-invoice, though not explicitly differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives, no prerequisites or context provided. The description is purely declarative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sharmaz/phoenixd-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server