Skip to main content
Glama

register_operator

Create a new operator account for the Lightning Wallet MCP server to manage Bitcoin Lightning wallets, access paid APIs, and control agent spending limits. Returns API key and recovery code that must be saved immediately.

Instructions

Register a new operator account. Returns API key and recovery code. SAVE THESE - they cannot be retrieved later!

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName for the operator account (optional)
emailNoOptional email for product updates and feature announcements

Implementation Reference

  • The implementation of the `register_operator` tool, which is a standalone exported function that registers a new operator with the Lightning Faucet API.
    export async function registerOperator(name?: string, email?: string): Promise<{
      operatorId: number;
      apiKey: string;
      recoveryCode: string;
    }> {
      const payload: Record<string, string> = {
        action: 'register',
        name: name || 'AI Agent Operator',
      };
      if (email) {
        payload.email = email;
      }
    
      const response = await fetch(API_BASE_URL, {
        method: 'POST',
        headers: {
          'Content-Type': 'application/json',
        },
        body: JSON.stringify(payload),
      });
    
      if (!response.ok) {
        throw new Error(`Request failed (HTTP ${response.status})`);
      }
    
      const result = await response.json() as RegisterResponse;
    
      if (!result.success) {
        throw new Error(result.error || 'Registration failed');
      }
    
      if (!result.api_key) {
        throw new Error('No API key returned');
      }
    
      return {
        operatorId: result.operator_id || 0,
        apiKey: result.api_key,
        recoveryCode: result.recovery_code || '',
      };
    }
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's a write operation (registration), returns sensitive credentials (API key and recovery code), and has irreversible consequences (credentials cannot be retrieved later). It doesn't cover rate limits or authentication requirements, but provides substantial operational context.

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?

Two sentences with zero waste - the first states the core purpose and return values, the second provides critical operational warning. The description is front-loaded with essential information and appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a registration tool with no annotations and no output schema, the description provides strong context about the irreversible nature of the operation and what credentials are returned. It could benefit from mentioning authentication requirements or whether this is a one-time operation, but covers the most critical aspects well.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents both parameters as optional. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 for adequate coverage through structured data alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Register a new operator account') and resource ('operator account'), distinguishing it from sibling tools like 'recover_account' or 'set_operator_key'. It explicitly mentions the creation of new credentials rather than modifying existing ones.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context about when to use this tool (for initial operator registration) and includes a critical warning about saving the returned credentials. However, it doesn't explicitly state when NOT to use it or mention alternatives like 'recover_account' for existing operators.

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