Skip to main content
Glama

Create a one-off Hypawave invoice (Path 3a seller)

create_invoice

Create a single-settlement invoice for a buyer to pay once. Returns invoice ID and access token for settlement, with activation fee to be paid before invoice goes live.

Instructions

Create a single-settlement invoice: one buyer pays once, creator-direct to your payment_destination. Returns the buyer payload (invoice_id + access_token — forward BOTH to the buyer, who settles it with pay_invoice) plus an activation fee bolt11 that must be paid before the invoice goes live. Attach a file first with attach_file(invoice_id=...) if selling a file — content seals at activation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYes
currencyNoDefault USD
due_dateYesISO date the invoice is due, e.g. 2026-07-31
expires_inNo
descriptionNo
client_emailYesBuyer contact email (required by the API)
company_nameNo
client_last_nameYes
client_first_nameYes
execution_webhookNo
pay_activation_feeNoPay the activation fee automatically via NWC (attach files first!)
payment_destinationYesYOUR Lightning Address or LNURL-pay URL
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes the return value (buyer payload + activation fee bolt11) and the activation prerequisite but lacks details on error behaviors, auth requirements, or rate limits.

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 concise single paragraph of three sentences, front-loading the main action and return value. It could be slightly more structured with bullet points, but it is efficient.

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?

Given no output schema and no annotations, the description explains the return value and activation sequence but omits detailed parameter explanations and error conditions. It is somewhat incomplete for a 12-parameter tool.

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 42%; the description adds context for payment_destination and the attach_file prerequisite but does not explain most parameters beyond the schema. It provides moderate additional meaning.

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 clearly states it creates a single-settlement invoice, specifying the verb 'create', resource 'invoice', and distinguishes from siblings by mentioning 'Path 3a seller' and referencing attach_file and pay_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?

The description indicates when to use (creating a one-off invoice) and implies prerequisites (attach file if selling, pay activation fee). It distinguishes from downstream tools like pay_invoice but does not explicitly state when not to use.

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/hypawave/mcp'

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