Skip to main content
Glama

Stop managed cluster

stop_managed_cluster
Destructive

Stop an existing managed Kubernetes cluster through provider-native deallocation. The cluster configuration and storage are preserved; start_managed_cluster resumes the existing cluster. Currently supported by AKS only; other managed providers fail closed through the provider capability check.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the target managed cluster. Optional when a cluster is selected.
cluster_nameNoExact name of the target managed cluster. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the description's real contribution is the reassurance that configuration and storage survive the stop and that non-AKS providers fail closed rather than silently no-op. That is meaningful behavioral context beyond the structured fields, though it doesn't say what happens to running workloads or whether the stop is graceful.

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?

Three sentences, front-loaded with the action, then what is preserved, then the provider constraint. No sentence is filler and the ordering matches how an agent needs the information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-param, zero-required mutation with no output schema, the definition covers action, data-preservation guarantees, recovery path, and provider support. Only the effect on in-flight workloads and the expected duration/failure modes are left implicit.

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 100% and both parameters already document that they are optional when a cluster is selected, so the description adds nothing about targeting semantics. Baseline 3 applies when the schema carries the full parameter burden.

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 names a specific verb and resource ("Stop an existing managed Kubernetes cluster") and pins down the mechanism ("provider-native deallocation"), which is clearly distinguishable from start_managed_cluster and from delete-flavored siblings.

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?

It explicitly routes the agent to start_managed_cluster for resumption and states the provider precondition (AKS only, others fail closed), which is actionable context. It stops short of naming when to choose this over a plain stop_cluster sibling, but the surrounding guidance is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.