Skip to main content
Glama

terminate_experiment

Stop and permanently delete a CloudLab experiment, removing all associated data. Use this tool to end experiments and free resources.

Instructions

Terminate an experiment (WARNING: destroys all data)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
experiment_idYesExperiment UUID (from list_experiments)

Implementation Reference

  • Handler for the 'terminate_experiment' tool. Extracts experiment_id from arguments, sends a DELETE request to the CloudLab API endpoint `/experiments/${experiment_id}`, and returns the result as text content.
    case "terminate_experiment": {
      const { experiment_id } = args as { experiment_id: string };
      const result = await cloudlabRequest(
        `/experiments/${experiment_id}`,
        "DELETE"
      );
      return {
        content: [
          {
            type: "text",
            text: `Experiment termination initiated: ${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • Schema definition and registration of the 'terminate_experiment' tool in the ListTools response, specifying input schema requiring 'experiment_id'.
    {
      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"],
      },
    },
Behavior4/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 effectively communicates the destructive nature ('destroys all data'), which is crucial for a mutation tool. However, it lacks details on permissions, reversibility, or response behavior, leaving some gaps in transparency.

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 a single sentence that directly states the purpose and includes a critical warning. Every word earns its place, with no unnecessary information or redundancy.

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 complexity (destructive mutation) and lack of annotations or output schema, the description is minimally adequate. It covers the core action and warning but omits details like error handling, confirmation steps, or return values, which could enhance completeness for such a high-stakes 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?

The schema description coverage is 100%, with the parameter 'experiment_id' fully documented in the schema. The description does not add any additional meaning or context beyond what the schema provides, such as format examples or usage tips, so it meets the baseline of 3.

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 ('Terminate') and the resource ('an experiment'), distinguishing it from siblings like create_experiment, extend_experiment, get_experiment, and list_experiments. It uses a precise verb that indicates a destructive operation, which is distinct from the read operations (get, list) and other maintenance actions (powercycle, reboot, reload).

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 for usage through the warning 'destroys all data', implying this tool should be used when permanent deletion is intended. However, it does not explicitly state when not to use it (e.g., vs. extend_experiment for modifications) or name specific alternatives, which prevents a score of 5.

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