Skip to main content
Glama

decode_invoice

Decode a BOLT11 invoice to extract amount, description, expiry, and destination without making a payment.

Instructions

Decode a BOLT11 invoice without paying it. Returns amount, description, expiry, and destination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bolt11YesBOLT11 invoice string to decode

Implementation Reference

  • The `decodeInvoice` method on `LightningFaucetClient` that executes the 'decode_invoice' tool logic. It sends a request with the bolt11 invoice to the API, then normalizes the response fields (amount, expiry, payment hash, etc.) into a consistent format.
    async decodeInvoice(bolt11: string): Promise<{
      amountSats: number;
      description: string;
      paymentHash: string;
      destination: string;
      expiresAt: string;
      isExpired: boolean;
      createdAt?: string;
      rawResponse: ApiResponse;
    }> {
      const result = await this.request<ApiResponse & {
        amount_sats?: number;
        num_satoshis?: string;
        description?: string;
        payment_hash?: string;
        destination?: string;
        timestamp?: string;
        expiry?: string;
        expires_at?: string;
        is_expired?: boolean;
      }>('decode_invoice', { invoice: bolt11 });
    
      const amountSats = result.amount_sats || parseInt(result.num_satoshis || '0', 10);
      const timestamp = result.timestamp ? parseInt(result.timestamp, 10) : 0;
      const expiry = result.expiry ? parseInt(result.expiry, 10) : 3600;
      const expiresAt = result.expires_at || new Date((timestamp + expiry) * 1000).toISOString();
      const isExpired = result.is_expired ?? (timestamp + expiry < Date.now() / 1000);
    
      return {
        amountSats,
        description: result.description || '',
        paymentHash: result.payment_hash || '',
        destination: result.destination || '',
        expiresAt,
        isExpired,
        createdAt: timestamp ? new Date(timestamp * 1000).toISOString() : undefined,
        rawResponse: result,
      };
    }
  • The private `request()` helper method used by `decodeInvoice` to make the actual HTTP API call. It sends the action name ('decode_invoice') along with the api_key and data payload.
    private async request<T extends ApiResponse>(
      action: string,
      data: Record<string, unknown> = {}
    ): Promise<T> {
      const payload = {
        action,
        api_key: this.apiKey,
        ...data,
      };
    
      const response = await fetch(API_BASE_URL, {
        method: 'POST',
        headers: {
          'Content-Type': 'application/json',
        },
        body: JSON.stringify(payload),
      });
    
      if (!response.ok) {
        // Don't include statusText in error — it may expose server internals
        throw new Error(`Request failed (HTTP ${response.status})`);
      }
    
      const result = await response.json() as T;
    
      if (!result.success) {
        throw new Error(result.error || 'Unknown API error');
      }
    
      return result;
    }
  • The string 'decode_invoice' is passed as the action parameter to `this.request()`, which is how the tool is effectively registered with the remote API.
    }>('decode_invoice', { invoice: bolt11 });
  • Type definition for the response from the 'decode_invoice' API call, including fields like amount_sats, num_satoshis, description, payment_hash, etc.
    const result = await this.request<ApiResponse & {
      amount_sats?: number;
      num_satoshis?: string;
      description?: string;
      payment_hash?: string;
      destination?: string;
      timestamp?: string;
      expiry?: string;
      expires_at?: string;
      is_expired?: boolean;
    }>('decode_invoice', { invoice: bolt11 });
  • Return type definition for the `decodeInvoice` method, mapping API response fields (snake_case) to camelCase properties.
    async decodeInvoice(bolt11: string): Promise<{
      amountSats: number;
      description: string;
      paymentHash: string;
      destination: string;
      expiresAt: string;
      isExpired: boolean;
      createdAt?: string;
      rawResponse: ApiResponse;
    }> {
Behavior4/5

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

Description explicitly states 'without paying it', which is key behavioral info. No annotations provided, so description carries burden well.

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 front-loaded purpose and return info. No wasted words.

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

Completeness5/5

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

For a simple tool with one parameter and no output schema, description is complete: explains action, constraints, and returns.

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 covers 100% of the single parameter with description. Description adds minimal extra meaning beyond 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?

Description clearly states it decodes a BOLT11 invoice without paying, listing return values. This distinguishes it from sibling tools like pay_invoice and create_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?

Implied usage as inspection-only tool, but no explicit when-to-use or when-not-to-use compared to alternatives like pay_invoice.

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/lightningfaucet/lightning-wallet-mcp'

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