Skip to main content
Glama

Update managed node pool

update_managed_node_pool
Destructive

Update a managed cluster's node pool in place with PATCH semantics: pass only the fields to change - at least one of count, autoscaling_enabled, autoscaling_min, autoscaling_max. Enabling autoscaling requires both bounds (existing values are kept when only one is passed). The change applies at the cloud provider; on scale-down the provider drains and removes nodes. externally_managed is a separate switch and must be sent ON ITS OWN (combining it with any other pool field is refused): true hands the pool's node count to something outside Ankra (a cluster autoscaler the customer runs at the provider) - from then on scale, update, delete and replace of the pool are refused until it is cleared, and list_managed_node_pools reports the provider's live count as observed_count; false returns the pool to Ankra and adopts the provider's live node count as the pool's count.

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": {
      "pool_name": "<pool_name>"
    },
    "name": "update_managed_node_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNew desired node count.
pool_nameYesName of the node pool to update (from list_managed_node_pools).
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.
autoscaling_maxNoNew autoscaling maximum node count.
autoscaling_minNoNew autoscaling minimum node count.
externally_managedNoSend on its own, without other pool fields. true: the pool's node count is owned outside Ankra (a customer-run cluster autoscaler) and Ankra refuses to scale, update, delete or replace the pool until this is cleared. false: Ankra manages the pool again and adopts the provider's live node count.
autoscaling_enabledNoEnable or disable autoscaling for the pool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description discloses provider-side application, node draining on scale-down, the refusal of scale/update/delete/replace while externally_managed is true, and that list_managed_node_pools then reports observed_count. These are exactly the operational consequences an agent needs before invoking a destructive mutation.

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 a single dense paragraph, but front-loaded with the PATCH contract before the edge-case rules. The externally_managed explanation is long and largely restates the schema property description, which is the main avoidable bulk.

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 8-parameter mutation with no output schema, the definition covers side effects, ordering constraints, and the externally_managed state machine. Nothing essential to calling it correctly is missing.

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 cross-parameter semantics the schema does not state: partial-bound behavior ('existing values are kept when only one is passed') and the hard rule that externally_managed cannot be combined with other pool fields. Minor redundancy with the externally_managed schema text keeps it from a 5.

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 opening sentence gives a specific verb and resource ('Update a managed cluster's node pool in place with PATCH semantics'), which immediately distinguishes it from add_managed_node_pool, delete_managed_node_pool and list_managed_node_pools. The patch-semantics framing tells an agent this is a partial-edit tool, not a create/replace.

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 states the precondition that at least one of count/autoscaling_enabled/autoscaling_min/autoscaling_max must be supplied, that enabling autoscaling requires both bounds, and that externally_managed must be sent alone. It does not name sibling alternatives (e.g. when to prefer update_node_group or add_managed_node_pool), so it stops short of full when/when-not routing.

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.