Skip to main content
Glama

get_wallet_service_info

Retrieve capabilities, supported encryption methods, and notification types for a connected Bitcoin Lightning wallet to enable payment functionality within language models.

Instructions

Get NWC capabilities, supported encryption and notification types of the connected lightning wallet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that retrieves wallet service information using the NWC client and formats it as JSON text content for the MCP response.
    async () => {
      const info = await client.getWalletServiceInfo();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(info, null, 2),
          },
        ],
      };
    }
  • The registration function that defines and registers the get_wallet_service_info tool on the MCP server, including name, description, and handler.
    export function registerGetWalletServiceInfoTool(
      server: McpServer,
      client: nwc.NWCClient
    ) {
      server.tool(
        "get_wallet_service_info",
        "Get NWC capabilities, supported encryption and notification types of the connected lightning wallet",
        async () => {
          const info = await client.getWalletServiceInfo();
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(info, null, 2),
              },
            ],
          };
        }
      );
    }
  • Invocation of the registration function during MCP server creation to register the tool.
    registerGetWalletServiceInfoTool(server, client);
Behavior3/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 implies a read-only operation ('Get') but doesn't specify whether it requires authentication, has rate limits, or details the return format. While it hints at querying a connected wallet, it lacks comprehensive behavioral context, resulting in an average score.

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 key action and details without any wasted words. It directly communicates the tool's function in a structured manner, making it highly concise and well-organized.

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 the tool does but lacks details on behavioral traits, usage context, or output format, leaving gaps that could hinder an AI agent's understanding in more complex scenarios.

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 the schema fully documents the absence of inputs. The description adds no parameter-specific information, which is appropriate here, but it doesn't compensate for any gaps since there are none. A baseline of 4 is applied as per the rules for zero parameters.

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 the specific information retrieved ('NWC capabilities, supported encryption and notification types of the connected lightning wallet'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this from sibling tools like 'get_info' or 'get_balance', which prevents a perfect score.

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 'get_info' or 'get_balance', nor does it mention any prerequisites or contextual cues for invocation. This lack of comparative or situational advice limits its utility for an AI agent.

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