Skip to main content
Glama

Upgrade managed cluster

upgrade_managed_cluster
Destructive

Upgrade a managed Kubernetes cluster's control-plane version to target_version at the cloud provider. Use list_managed_k8s_options with the cluster target first to see the current version and the available upgrade candidates. Runs as a tracked operation; node pools follow the provider's own upgrade behaviour. The cluster must have finished provisioning and be free of in-progress operations. Not reversible - managed control planes cannot be downgraded.

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": {
      "target_version": "<target_version>"
    },
    "name": "upgrade_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.
target_versionYesTarget Kubernetes version (an available upgrade from list_managed_k8s_options).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, but the description adds material context beyond them: the operation is tracked, node pools follow the provider's own upgrade behaviour, the cluster must be fully provisioned with no in-progress operations, and the change is irreversible because managed control planes cannot be downgraded. That is exactly the kind of consequence disclosure an agent needs before a destructive call.

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?

Four short sentences, front-loaded with what the tool does, then the read-first step, then the operational semantics, then the irreversibility warning. Nothing is repeated from the title or schema and each sentence 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 destructive, non-idempotent mutation with no output schema, the description covers scope, prerequisites, side effects on node pools, and irreversibility. The main remaining gap is that it says the call 'runs as a tracked operation' without pointing at how to follow it (e.g. wait_for_execution or the execution-status siblings), which an agent performing an async upgrade would likely need.

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%, so the three parameters are already documented, including that target_version must be an available upgrade from list_managed_k8s_options. The description reinforces the target-version selection flow but adds no new format, default, or identifier-resolution detail beyond the schema, which is the expected baseline.

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 ('Upgrade a managed Kubernetes cluster's control-plane version') and scopes it to the managed control plane at the cloud provider, which implicitly separates it from upgrade_cluster/roll_cluster_to_version and upgrade_cluster_agent. It never names those siblings explicitly, so the differentiation is inferred rather than stated.

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 gives a concrete prerequisite workflow ('Use list_managed_k8s_options with the cluster target first to see the current version and the available upgrade candidates') and states gating conditions (cluster finished provisioning, no in-progress operations). It stops short of naming which alternative tool to use for non-managed clusters or node-pool upgrades, so the when-not guidance is only partial.

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.