Skip to main content
Glama
lnfi-network

RGB Lightning Network MCP Server

by lnfi-network

rgb_get_network_info

Retrieve network status and configuration details from the RGB Lightning Node to monitor connectivity and operational parameters.

Instructions

Get network information from the RGB node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.ts:152-165 (registration)
    Registration of the 'rgb_get_network_info' MCP tool, including description, empty input schema, and inline handler that calls the RGB client's getNetworkInfo method and returns formatted JSON or error.
    server.tool(
      'rgb_get_network_info',
      'Get network information from the RGB node',
      {},
      async ({}) => {
        try {
          const networkInfo = await rgbClient.getNetworkInfo();
          return { content: [{ type: 'text', text: JSON.stringify(networkInfo, null, 2) }] };
        } catch (error) {
          const errorMessage = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: `Error: ${errorMessage}` }], isError: true };
        }
      }
    );
  • The inline handler function executes the tool logic by fetching network information via rgbClient and responding with JSON.
    server.tool(
      'rgb_get_network_info',
      'Get network information from the RGB node',
      {},
      async ({}) => {
        try {
          const networkInfo = await rgbClient.getNetworkInfo();
          return { content: [{ type: 'text', text: JSON.stringify(networkInfo, 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 SDK call to retrieve network information from the RGB node.
    async getNetworkInfo() {
      return await this.client.node.getNetworkInfo();
    }
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 if this is a read-only operation, requires authentication, has rate limits, or what the output format might be, leaving significant gaps in transparency.

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 a single, efficient sentence with no wasted words, clearly front-loading the purpose. It's appropriately sized for a simple tool with no parameters, making it easy to parse quickly.

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 annotations and no output schema, the description is incomplete for a tool that likely returns structured network data. It doesn't explain what 'network information' includes (e.g., connections, peers, status) or the response format, leaving the agent uncertain about behavior and outputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so no parameter information is needed. The description doesn't add param details, but that's appropriate here, meeting the baseline for a zero-param tool without redundancy.

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 ('Get') and resource ('network information from the RGB node'), making the purpose understandable. It distinguishes from siblings like rgb_get_node_info and rgb_get_node_status by specifying 'network' information, though it doesn't explicitly contrast them.

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_get_node_info or rgb_get_node_status. It lacks any context about prerequisites, timing, or comparisons to sibling tools, leaving the agent without usage direction.

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