Skip to main content
Glama
lnfi-network

RGB Lightning Network MCP Server

by lnfi-network

rgb_get_node_info

Retrieve RGB Lightning node details such as ID, version, and network connectivity status to monitor node health and operational readiness.

Instructions

Get RGB node information including ID, version, and network status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The inline anonymous async function that serves as the handler for the MCP tool 'rgb_get_node_info'. It calls rgbClient.getNodeInfo(), formats the result as JSON text response, and handles errors.
    async ({}) => {
      try {
        const nodeInfo = await rgbClient.getNodeInfo();
        return { content: [{ type: 'text', text: JSON.stringify(nodeInfo, null, 2) }] };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return { content: [{ type: 'text', text: `Error: ${errorMessage}` }], isError: true };
      }
    }
  • src/server.ts:20-33 (registration)
    The server.tool() registration of the 'rgb_get_node_info' MCP tool, specifying name, description, empty input schema ({}), and inline handler function.
    server.tool(
      'rgb_get_node_info',
      'Get RGB node information including ID, version, and network status',
      {},
      async ({}) => {
        try {
          const nodeInfo = await rgbClient.getNodeInfo();
          return { content: [{ type: 'text', text: JSON.stringify(nodeInfo, null, 2) }] };
        } catch (error) {
          const errorMessage = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: `Error: ${errorMessage}` }], isError: true };
        }
      }
    );
  • Empty input schema object for the tool (no parameters required).
    {},
  • Supporting helper method in RGBApiClientWrapper class that wraps the SDK's node.getNodeInfo() call, used by the tool handler.
    async getNodeInfo() {
      return await this.client.node.getNodeInfo();
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it's a 'Get' operation, implying read-only behavior, but doesn't disclose any behavioral traits such as error conditions, rate limits, authentication needs, or what happens if the node is unavailable. This is a significant gap for a tool with no annotation coverage.

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 that front-loads the purpose ('Get RGB node information') and specifies key details. There is no wasted text, and it is appropriately sized for a simple tool.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what information is retrieved, but lacks details on behavioral aspects and usage context, making it incomplete for fully informed tool selection by an AI agent.

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, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info beyond the schema, but with no parameters, this is acceptable, aligning with the baseline expectation for zero-param tools.

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 verb 'Get' and the resource 'RGB node information', specifying what information is retrieved (ID, version, network status). It distinguishes from some siblings like 'rgb_get_network_info' by focusing on node-specific details, though it doesn't explicitly differentiate from 'rgb_get_node_status'.

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 is provided on when to use this tool versus alternatives. It doesn't mention when this tool is appropriate compared to siblings like 'rgb_get_node_status' or 'rgb_get_network_info', nor does it specify any prerequisites or exclusions for usage.

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