Skip to main content
Glama

get_info

Retrieve service details such as version, operational status, usage limits, and available features for the Lightning Wallet MCP server.

Instructions

Get service information including version, status, limits, and supported features.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getInfo implementation in the LightningFaucetClient class.
    async getInfo(): Promise<{
      version: string;
      apiVersion: string;
      status: string;
      maxPaymentSats: number;
      minPaymentSats: number;
      supportedFeatures: string[];
      rawResponse: ApiResponse;
    }> {
      const result = await this.request<ApiResponse & {
        version?: string;
        api_version?: string;
        status?: string;
        max_payment_sats?: number;
        min_payment_sats?: number;
        supported_features?: string[];
      }>('get_info');
    
      return {
        version: result.version || '2.0.0',
        apiVersion: result.api_version || '1.0',
        status: result.status || 'operational',
        maxPaymentSats: result.max_payment_sats || 1000000,
        minPaymentSats: result.min_payment_sats || 1,
        supportedFeatures: result.supported_features || ['l402', 'webhooks', 'lightning_address'],
        rawResponse: result,
      };
    }
  • src/index.ts:610-617 (registration)
    The get_info tool registration.
      name: 'get_info',
      description: 'Get service information including version, status, limits, and supported features.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • The MCP tool call handler for get_info.
    case 'get_info': {
      GetInfoSchema.parse(args);
      const result = await session.requireClient().getInfo();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              success: true,
              version: result.version,
              api_version: result.apiVersion,
              status: result.status,
              max_payment_sats: result.maxPaymentSats,
              min_payment_sats: result.minPaymentSats,
              supported_features: result.supportedFeatures,
            }, null, 2),
          },
        ],
      };
    }
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 of behavioral disclosure. While it implies a read-only operation by using 'Get,' it doesn't specify authentication requirements, rate limits, error conditions, or what format the information is returned in. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 clearly communicates the tool's purpose without any wasted words. It's appropriately sized for a simple read operation and front-loads the key information.

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 adequate but has clear gaps. It explains what information is retrieved but doesn't address behavioral aspects like authentication or response format. For a read-only tool with no structured metadata, more context about how to interpret the results would be helpful.

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 parameters. The description appropriately doesn't mention parameters, which is correct for a parameterless tool. This earns a baseline score of 4 since no parameter information is needed.

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 resource ('service information') with specific details about what information is included (version, status, limits, supported features). However, it doesn't differentiate itself from potential sibling tools like 'get_rate_limits' or 'whoami' that might provide overlapping or related information.

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. With sibling tools like 'get_rate_limits' and 'whoami' that might provide related information, there's no indication of when this comprehensive service information tool is preferred over more specific tools.

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/lightningfaucet/lightning-wallet-mcp'

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