Skip to main content
Glama

start_cluster

Idempotent

Start a compute cluster by name, optionally in a named workspace, and safely repeat the request if the cluster is already running.

Instructions

Start a cluster. Safe to repeat.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "start_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
workspaceNoNamed workspace. Omit to use the default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare idempotentHint=true through openWorldHint=false, and "Safe to repeat" merely restates idempotency rather than adding context. It says nothing about what happens if the cluster is already running, whether the call blocks until ready, or what permissions are needed for this mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loaded, but the second sentence duplicates the idempotentHint annotation instead of contributing new information, making it terse rather than efficient.

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 mutating lifecycle tool with no output schema and a required, undocumented parameter, the description leaves key questions open: expected return, effect on a running cluster, and completion semantics. It is under-specified for the tool's complexity.

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

Parameters2/5

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

The schema documents only the optional workspace parameter; the required `name` has no description, leaving 50% coverage. The description adds no meaning to either parameter, so it does not compensate for the gap.

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?

"Start a cluster" is a specific verb plus resource, so the basic action is unambiguous. It does not distinguish itself from siblings such as list_clusters or terminate_cluster, but the core purpose is clear.

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?

There is no guidance on when to call this versus list_clusters (to check state first) or what preconditions apply. "Safe to repeat" is a behavioral note rather than usage guidance, so the agent must infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.