Skip to main content
Glama

reactivate_agent

Reactivate a deactivated agent in the Lightning Wallet MCP server to restore its ability to manage Bitcoin Lightning payments and access paid APIs using the operator key.

Instructions

Reactivate a previously deactivated agent. REQUIRES OPERATOR KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesAgent ID to reactivate

Implementation Reference

  • The actual implementation of the reactivateAgent method in the LightningFaucetClient class.
     * Reactivate an agent
     */
    async reactivateAgent(agentId: number): Promise<{
      agentId: number;
      message: string;
      rawResponse: ApiResponse;
    }> {
      const result = await this.request<ApiResponse & { message?: string }>('update_agent', {
        agent_id: agentId,
        updates: { is_active: true },
      });
    
      return {
        agentId,
        message: result.message || 'Agent reactivated',
        rawResponse: result,
      };
    }
  • The MCP tool handler for the 'reactivate_agent' tool, which calls the client method.
    case 'reactivate_agent': {
      const parsed = ReactivateAgentSchema.parse(args);
      const result = await session.requireClient().reactivateAgent(parsed.agent_id);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              success: true,
              message: result.message || 'Agent reactivated',
              agent_id: result.agentId,
            }, null, 2),
          },
        ],
      };
    }
  • Input validation schema for the 'reactivate_agent' tool.
    const ReactivateAgentSchema = z.object({
      agent_id: z.number().int().positive().describe('Agent ID to reactivate'),
    });
  • src/index.ts:571-580 (registration)
    Registration of the 'reactivate_agent' tool within the MCP server definition.
      name: 'reactivate_agent',
      description: 'Reactivate a previously deactivated agent. REQUIRES OPERATOR KEY.',
      inputSchema: {
        type: 'object',
        properties: {
          agent_id: { type: 'integer', description: 'Agent ID to reactivate' },
        },
        required: ['agent_id'],
      },
    },
Behavior3/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 discloses the operator key requirement, which is a critical behavioral trait. However, it lacks details on other aspects like potential side effects (e.g., reactivation of billing or permissions), error conditions, or rate limits, leaving gaps in behavioral 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?

The description is extremely concise and front-loaded, consisting of just two sentences that efficiently convey the purpose and key requirement. Every word earns its place, with no redundant or unnecessary information, making it highly effective for quick understanding.

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 complexity of reactivating an agent (a mutation operation) and the lack of annotations and output schema, the description is minimally complete. It covers the purpose and key prerequisite but omits details on behavior, return values, or error handling, which are important for such an operation.

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%, with the parameter 'agent_id' fully documented in the schema. The description does not add any additional meaning or context beyond what the schema provides, such as format constraints or examples. The baseline score of 3 reflects adequate coverage from the schema 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 ('reactivate') and resource ('previously deactivated agent'), distinguishing it from sibling tools like 'deactivate_agent' and 'create_agent'. It precisely defines what the tool does without being vague or tautological.

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 explicitly states 'REQUIRES OPERATOR KEY', providing clear context about prerequisites. However, it does not specify when to use this tool versus alternatives like 'create_agent' or 'recover_account', nor does it mention exclusions or other contextual guidance beyond the key requirement.

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