Skip to main content
Glama

powercycle_node

Perform a hard reboot of a CloudLab experiment node to resolve unresponsive states or apply hardware-level resets.

Instructions

Power cycle a node (hard reboot)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
experiment_idYesExperiment UUID (from list_experiments)
nodeYesNode client_id

Implementation Reference

  • Handler implementation for the 'powercycle_node' tool. Extracts experiment_id and node from input arguments, sends a POST request to CloudLab API `/experiments/{experiment_id}/node/{node}/powercycle`, and returns the formatted result.
    case "powercycle_node": {
      const { experiment_id, node } = args as {
        experiment_id: string;
        node: string;
      };
      const result = await cloudlabRequest(
        `/experiments/${experiment_id}/node/${node}/powercycle`,
        "POST"
      );
      return {
        content: [
          {
            type: "text",
            text: `Power cycle initiated for node ${node}: ${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • src/index.ts:203-221 (registration)
    Tool registration in list_tools response, defining name, description, and input schema for 'powercycle_node' requiring experiment_id and node.
    {
      name: "powercycle_node",
      description: "Power cycle a node (hard reboot)",
      inputSchema: {
        type: "object",
        properties: {
          experiment_id: {
            type: "string",
            description: "Experiment UUID (from list_experiments)",
          },
          node: {
            type: "string",
            description: "Node client_id",
          },
        },
        required: ["experiment_id", "node"],
      },
    },
    {
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose potential impacts (e.g., service interruption, data loss), permissions required, rate limits, or what happens if the node is unavailable. 'Hard reboot' implies forceful restart but lacks 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?

The description is a single, efficient sentence with zero waste. It is front-loaded with the core action and resource, and the parenthetical 'hard reboot' adds useful clarification without verbosity.

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?

For a destructive tool like power cycling with no annotations and no output schema, the description is insufficient. It doesn't cover behavioral risks, success/failure outcomes, or integration with sibling tools (e.g., relationship to 'list_experiments' for getting experiment_id). More context is needed given the tool's potential impact.

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 ('experiment_id' and 'node') adequately. The description adds no additional parameter semantics beyond implying the node is part of an experiment, which is already suggested by the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('power cycle') and resource ('a node'), with 'hard reboot' providing additional technical clarification. It distinguishes from siblings like 'reboot_node' (likely soft reboot) and 'reboot_all_nodes' (multiple nodes).

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 guidance is provided on when to use this tool versus alternatives like 'reboot_node' or 'reload_node'. The description doesn't mention prerequisites, dependencies, or scenarios where a hard reboot is preferred over other options.

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/ArdaGurcan/cloudlab-mcp'

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