Skip to main content
Glama

get_experiment

Retrieve detailed status and node states for a specific CloudLab experiment using its UUID to monitor experiment progress and troubleshoot issues.

Instructions

Get detailed status of a specific experiment including node states

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
experiment_idYesExperiment UUID (from list_experiments)

Implementation Reference

  • Handler for 'get_experiment' tool: extracts experiment_id from arguments, calls cloudlabRequest to fetch experiment details from API, and returns JSON-formatted result as text content.
    case "get_experiment": {
      const { experiment_id } = args as { experiment_id: string };
      const result = await cloudlabRequest(`/experiments/${experiment_id}`);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Tool schema definition including name, description, and input schema requiring 'experiment_id' string.
    {
      name: "get_experiment",
      description: "Get detailed status of a specific experiment including node states",
      inputSchema: {
        type: "object",
        properties: {
          experiment_id: {
            type: "string",
            description: "Experiment UUID (from list_experiments)",
          },
        },
        required: ["experiment_id"],
      },
    },
  • src/index.ts:97-255 (registration)
    Registration of all tools including 'get_experiment' via ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "list_experiments",
            description: "List all your CloudLab experiments",
            inputSchema: {
              type: "object",
              properties: {},
              required: [],
            },
          },
          {
            name: "create_experiment",
            description: "Create a new CloudLab experiment from a profile",
            inputSchema: {
              type: "object",
              properties: {
                project: {
                  type: "string",
                  description: "Project name (e.g., 'UCY-CS499-DC')",
                },
                profile_name: {
                  type: "string",
                  description: "Profile name (e.g., 'small-lan')",
                },
                profile_project: {
                  type: "string",
                  description: "Project that owns the profile (e.g., 'PortalProfiles')",
                },
                name: {
                  type: "string",
                  description: "Optional experiment name (auto-generated if not provided)",
                },
                bindings: {
                  type: "object",
                  description: "Optional profile parameter bindings (e.g., {nodeCount: '2', phystype: 'c220g1'})",
                },
              },
              required: ["project", "profile_name", "profile_project"],
            },
          },
          {
            name: "get_experiment",
            description: "Get detailed status of a specific experiment including node states",
            inputSchema: {
              type: "object",
              properties: {
                experiment_id: {
                  type: "string",
                  description: "Experiment UUID (from list_experiments)",
                },
              },
              required: ["experiment_id"],
            },
          },
          {
            name: "reboot_node",
            description: "Reboot a specific node in an experiment",
            inputSchema: {
              type: "object",
              properties: {
                experiment_id: {
                  type: "string",
                  description: "Experiment UUID (from list_experiments)",
                },
                node: {
                  type: "string",
                  description: "Node client_id (e.g., 'node0')",
                },
              },
              required: ["experiment_id", "node"],
            },
          },
          {
            name: "reboot_all_nodes",
            description: "Reboot all nodes in an experiment",
            inputSchema: {
              type: "object",
              properties: {
                experiment_id: {
                  type: "string",
                  description: "Experiment UUID (from list_experiments)",
                },
              },
              required: ["experiment_id"],
            },
          },
          {
            name: "reload_node",
            description: "Reload/reimage a node with its disk image",
            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"],
            },
          },
          {
            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"],
            },
          },
          {
            name: "extend_experiment",
            description: "Extend the expiration time of an experiment",
            inputSchema: {
              type: "object",
              properties: {
                experiment_id: {
                  type: "string",
                  description: "Experiment UUID (from list_experiments)",
                },
                hours: {
                  type: "number",
                  description: "Number of hours to extend",
                },
              },
              required: ["experiment_id", "hours"],
            },
          },
          {
            name: "terminate_experiment",
            description: "Terminate an experiment (WARNING: destroys all data)",
            inputSchema: {
              type: "object",
              properties: {
                experiment_id: {
                  type: "string",
                  description: "Experiment UUID (from list_experiments)",
                },
              },
              required: ["experiment_id"],
            },
          },
        ],
      };
    });
Behavior2/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 states this is a read operation ('Get'), implying it's non-destructive, but doesn't cover aspects like authentication needs, rate limits, error handling, or what 'detailed status' includes (e.g., format, timestamps). For a tool with zero annotation coverage, this is inadequate.

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 core purpose ('Get detailed status of a specific experiment') and adds a key detail ('including node states') without waste. Every word earns its place, making it highly concise and well-structured.

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 moderate complexity (read operation with one parameter) and no annotations or output schema, the description is minimally complete. It covers the basic purpose but lacks details on behavior, usage context, and return values, leaving gaps that could hinder effective agent invocation.

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?

The input schema has 100% description coverage, with 'experiment_id' documented as 'Experiment UUID (from list_experiments)'. The description adds no additional parameter semantics beyond this, such as format details or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb 'Get' and the resource 'detailed status of a specific experiment including node states', which specifies what the tool does. It distinguishes from siblings like 'list_experiments' by focusing on a single experiment's details rather than listing multiple. However, it doesn't explicitly contrast with all siblings (e.g., 'create_experiment'), so it's not a perfect 5.

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. It doesn't mention prerequisites (e.g., needing an experiment_id from 'list_experiments'), exclusions, or compare to other read operations. This leaves the agent with minimal context for tool selection among siblings.

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