Skip to main content
Glama

get_info

Retrieve wallet capabilities and node information for Bitcoin Lightning payments through Nostr Wallet Connect.

Instructions

Get NWC capabilities of the connected lightning wallet, and general information about the wallet and underlying lightning node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'get_info' tool logic: calls client.getInfo() and returns the wallet/node information as formatted JSON text.
    async () => {
      const info = await client.getInfo();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(info, null, 2),
          },
        ],
      };
    }
  • The registration function for the 'get_info' tool, which calls server.tool() to register the tool name, description, and handler on the MCP server.
    export function registerGetInfoTool(server: McpServer, client: nwc.NWCClient) {
      server.tool(
        "get_info",
        "Get NWC capabilities of the connected lightning wallet, and general information about the wallet and underlying lightning node",
        async () => {
          const info = await client.getInfo();
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(info, null, 2),
              },
            ],
          };
        }
      );
    }
  • Calls the registerGetInfoTool function to register the 'get_info' tool during MCP server creation.
    registerGetInfoTool(server, client);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but lacks details on permissions, rate limits, error handling, or response format, which are critical for a tool interacting with a wallet.

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 single, efficient sentence that front-loads the key action ('Get') and specifies the information types. It avoids unnecessary words, though it could be slightly more structured by separating the different information categories.

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 the complexity of interacting with a lightning wallet and the absence of annotations and output schema, the description is incomplete. It doesn't explain what specific data is returned (e.g., balance, node ID, capabilities list), error conditions, or dependencies, leaving gaps for 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose without redundant parameter details, aligning with the baseline expectation for zero-parameter 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 tool's purpose: retrieving NWC capabilities, wallet information, and lightning node details. It specifies the resource (connected lightning wallet) and the type of information returned, though it doesn't explicitly differentiate from sibling tools like 'get_wallet_service_info' or 'get_balance'.

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 explicit guidance is provided on when to use this tool versus alternatives. While the description implies it's for general information retrieval, it doesn't specify use cases, prerequisites, or contrast with siblings such as 'get_wallet_service_info' for more specific data.

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/getAlby/nwc-mcp-server'

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