Skip to main content
Glama

terminate_cluster

DestructiveIdempotent

Terminate a running cluster with required confirmation, or use dry-run mode to preview the destructive action before execution.

Instructions

Terminate a running cluster. Requires confirm=true; use dry_run=true to preview.

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": "terminate_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmNoMust be true to execute this destructive operation.
dry_runNoPreview what would happen without changing anything.
workspaceNoNamed workspace. Omit to use the default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds the confirm gate and the preview path, but says nothing about what is lost on termination (in-flight jobs, data, recoverability) or how a repeat call on an already-terminated cluster behaves despite idempotentHint.

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?

Two short sentences, no filler, and the action is front-loaded ahead of the precondition and the preview hint.

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?

With no output schema and four parameters, the definition covers the gating mechanics but omits consequences of a destructive, irreversible action. An agent can invoke it correctly, but cannot tell a user what termination actually costs.

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 coverage is 75% and the schema itself already explains confirm ('Must be true to execute this destructive operation') and dry_run. The description only restates those two flags and says nothing about name or workspace, so it adds no meaning beyond the structured fields.

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 states a specific verb and resource with scope: 'Terminate a running cluster.' That is enough to separate it from read/list siblings and from drop_table, though it never names start_cluster as the inverse operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives operational guidance ('use dry_run=true to preview') and a hard precondition ('Requires confirm=true'), which is genuinely useful. It stops short of saying when to choose termination versus any alternative, or when termination is inappropriate.

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