Skip to main content
Glama

Change control plane

change_control_plane
Destructive

Change the control plane of an Ankra-provisioned self-managed cluster. Provide exactly ONE of: count (1 or 3; additionally 5 on Proxmox VE - etcd quorum needs an odd number) or instance_type (resizes every control plane node). GROWING the count (1 -> 3, 3 -> 5) happens LIVE on a running cluster: the new control planes provision and join etcd without downtime, and the answer carries the operation to follow. REDUCING the count is applied offline: stop the cluster (the stop preserves its state and the start restores it), apply the change, then start_cluster. instance_type changes roll one controller at a time on a running cluster with 3 or more controllers. On a RUNNING cluster with a SINGLE controller (Hetzner), changing instance_type resizes that one server in place and TAKES THE KUBERNETES API DOWN for a few minutes (typically 3 to 8) while it reboots: workloads already running on workers keep running, but kubectl, deployments, controllers and the Ankra agent pause until it is back. That call REQUIRES accept_api_downtime=true and is refused without it; only set it when the user has explicitly accepted the API downtime, and tell them about it first. The alternatives are growing to 3 controllers first (no downtime) or applying the change offline on a stopped cluster. Call list_node_groups first - its control_plane section reports the current count/instance type, whether a change is possible right now, and in which mode.

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

Input Schema

NameRequiredDescriptionDefault
countNoNew control plane count (1 or 3; also 5 on Proxmox VE). Exactly one aspect per call.
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.
instance_typeNoNew provider instance type for every control plane node. Exactly one aspect per call.
accept_api_downtimeNoRequired (true) to change instance_type of a RUNNING cluster that has only ONE control plane: the user accepts that the Kubernetes API is down for a few minutes while that server reboots on the new type. Ignored otherwise. Never set it without the user's explicit acceptance of the downtime.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / accept_api_downtime
      Added value: +{
      +  "description": "Required (true) to change instance_type of a RUNNING cluster that has only ONE control plane: the user accepts that the Kubernetes API is down for a few minutes while that server reboots on the new type. Ignored otherwise. Never set it without the user's explicit acceptance of the downtime.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, and the description goes well beyond them: etcd quorum requiring odd counts, live join without downtime, one-controller-at-a-time rolling for instance_type, and a 3-8 minute API outage on single-controller Hetzner clusters gated behind accept_api_downtime=true. The only gap is that it does not say what the returned 'operation to follow' looks like or how to track it, though it does mention the answer carries an operation.

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

Conciseness4/5

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

It is long, but front-loaded with the core action and the one-of-two-aspects rule before the operational detail, and every sentence carries distinct information (quorum, live growth, offline shrink, rolling resize, downtime gate). The single-controller Hetzner paragraph is dense and could be tightened, but nothing is redundant.

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

Completeness5/5

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

For a destructive, multi-mode cluster mutation with no output schema, the description covers the decision inputs an agent needs: current-state discovery via list_node_groups, mode selection, downtime consent, and the offline stop/start sequence. Nothing material is left to inference.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: why count must be odd (etcd quorum), that 5 is Proxmox-only, that instance_type resizes every control plane node, and the precise condition under which accept_api_downtime is required versus ignored. It also enforces the 'exactly ONE aspect per call' constraint that the schema only hints at per-property.

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 opens with a specific verb and resource ('Change the control plane of an Ankra-provisioned self-managed cluster') and immediately scopes it to exactly two aspects, count or instance_type. That distinguishes it cleanly from siblings like scale_workers, add_node_group, update_node_group and roll_cluster_to_version, which an agent could otherwise confuse with control-plane resizing.

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

Usage Guidelines5/5

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

It states explicit preconditions ('Call list_node_groups first'), the live-vs-offline split for growing versus reducing count, and names concrete alternatives (grow to 3 controllers first, or apply offline on a stopped cluster). It also spells out the exact sequence for the offline path: stop_cluster, apply, start_cluster.

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.