Skip to main content
Glama

Start managed cluster

start_managed_cluster
Destructive

Start a stopped managed Kubernetes cluster through the provider, which resumes the existing cluster with its preserved configuration and storage. 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": "start_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

A3.8/5.0
Behavior3/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=true), the description adds that configuration and storage are preserved and that unsupported providers fail closed in the capability check. However, it does not reconcile the declared destructiveHint=true with the reassuring 'preserved configuration and storage' wording, nor explain why the operation is non-idempotent (e.g., repeated starts erroring).

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 sentences with zero filler: the action and its effect come first, the provider-support caveat second. Every clause carries distinct 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-optional-parameter tool with full schema coverage and no output schema, the description covers effect, provider support, and failure mode. The only meaningful gap is error surfacing and idempotency behavior, which is a modest omission rather than a blocking one.

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 description coverage is 100%, and both cluster_id and cluster_name are fully documented there, including that either is optional when a cluster is selected. The description adds no selector precedence or fallback rule, so it neither detracts from nor improves on the schema.

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?

States a specific verb and resource ('Start a stopped managed Kubernetes cluster') and adds the distinguishing qualifier 'managed' plus provider routing, which separates it from start_cluster. It stops short of naming the non-managed sibling, so an agent must infer the split from the adjective alone.

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?

Clear preconditions are given: the cluster must be stopped and managed, and the tool resumes it rather than creating anything. The AKS-only scope and the fail-closed behavior for other providers tell the agent exactly when this call will succeed versus error, though no alternative tool is named for the unsupported-provider case.

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.