Skip to main content
Glama
lnfi-network

RGB Lightning Network MCP Server

by lnfi-network

rgb_send_bitcoin

Send Bitcoin to a specified address using the RGB Lightning Network MCP Server. This tool processes on-chain Bitcoin transactions by accepting a recipient address and amount in satoshis.

Instructions

Send Bitcoin to an address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe recipient Bitcoin address
amountYesThe amount to send in satoshis

Implementation Reference

  • src/server.ts:167-183 (registration)
    Registration of the 'rgb_send_bitcoin' MCP tool, including input schema and handler function that delegates to RGBApiClientWrapper.sendBitcoin(address, amount) method.
    server.tool(
      'rgb_send_bitcoin',
      'Send Bitcoin to an address',
      {
        address: z.string().describe('The recipient Bitcoin address'),
        amount: z.number().describe('The amount to send in satoshis'),
      },
      async ({ address, amount }) => {
        try {
          const result = await rgbClient.sendBitcoin(address, amount);
          return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
        } catch (error) {
          const errorMessage = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: `Error: ${errorMessage}` }], isError: true };
        }
      }
    );
  • Input schema for the rgb_send_bitcoin tool using Zod validation.
    {
      address: z.string().describe('The recipient Bitcoin address'),
      amount: z.number().describe('The amount to send in satoshis'),
    },
  • Handler function that executes the tool logic by calling the client wrapper's sendBitcoin method.
    async ({ address, amount }) => {
      try {
        const result = await rgbClient.sendBitcoin(address, amount);
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return { content: [{ type: 'text', text: `Error: ${errorMessage}` }], isError: true };
      }
    }
  • Helper method in RGBApiClientWrapper that wraps the underlying SDK's onchain.sendBtc call for sending Bitcoin.
    async sendBitcoin(address: string, amount: number) {
      return await this.client.onchain.sendBtc({ address, amount });
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention whether this is a read/write operation, permission requirements, transaction finality, fee implications, rate limits, or error conditions, leaving significant gaps for a financial transaction tool.

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?

The description is extremely concise with a single sentence that directly states the tool's purpose. There's no unnecessary information or repetition, making it front-loaded and efficient. Every word earns its place in this minimal but clear statement.

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?

For a Bitcoin sending tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after sending (transaction ID, confirmation status, error handling), nor does it address security implications or typical workflow context. The combination of missing behavioral transparency and output information creates significant gaps.

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% description coverage, clearly documenting both parameters. The description adds no additional meaning beyond what's in the schema, such as address format validation or satoshi conversion details. With high schema coverage, the baseline score of 3 is appropriate as the schema handles parameter documentation adequately.

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 action ('Send') and resource ('Bitcoin'), specifying what the tool does. It distinguishes from siblings like 'rgb_send_assets' by focusing on Bitcoin specifically, but doesn't explicitly contrast with 'rgb_pay_lightning_invoice' which also involves Bitcoin transfers, leaving some ambiguity.

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?

The description provides no guidance on when to use this tool versus alternatives like 'rgb_send_assets' for other assets or 'rgb_pay_lightning_invoice' for Lightning payments. There's no mention of prerequisites, network conditions, or typical use cases, offering minimal context for selection.

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/lnfi-network/rgb-mcp-server'

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