Skip to main content
Glama

Scale workers

scale_workers
Destructive

Scale the workers of an Ankra-provisioned self-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, Ankra Cloud, Proxmox VE, or HPE Morpheus). With node_group_name, scales that node group to worker_count (0-100; the target is clamped into the group's autoscaling bounds when autoscaling is enabled); without it, performs the legacy whole-cluster scale to worker_count (1-10; refused while any node group has autoscaling enabled - scale the group directly instead). The cluster must be online and free of in-progress operations. New workers provision in the background. On scale-down the highest-index workers drain one at a time through the eviction API, honouring PodDisruptionBudgets, and are then terminated; a worker whose drain a PodDisruptionBudget refuses is kept in service and the scale-down is withdrawn for it, so the group can settle above worker_count. Call list_node_groups first to see the current counts, and again afterwards to confirm them.

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

Input Schema

NameRequiredDescriptionDefault
countNoAlias for worker_count.
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
force_drainNoScale-down only. Remove the workers without honouring PodDisruptionBudgets: each is drained the way a cluster teardown drains it, and removed even when its drain is refused or the node is unreachable. Off by default: a scale-down drains each worker through its budgets and keeps a worker whose drain is refused. Set it only when the user explicitly asks to remove a worker anyway - for example a dead worker, or one a budget keeps refusing - never on your own.
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.
worker_countNoDesired worker count. Required ('count' is accepted as an alias).
node_group_nameNoNode group to scale (from list_node_groups). Omit for the legacy whole-cluster scale.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true / idempotentHint=false annotations: workers provision asynchronously, scale-down drains highest-index workers one at a time through the eviction API honouring PodDisruptionBudgets, refused drains are kept in service and the scale-down withdrawn, so the group may settle above worker_count. It also explains force_drain's semantics and when it is acceptable to use.

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?

Front-loaded with purpose and mode split, then prerequisites, then drain mechanics, then the recommended workflow — a logical order with no filler sentences. It is dense to the point of being long, and the provider enumeration is low-value for tool selection, 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, non-idempotent mutation with no output schema, the description covers scope, mode selection, prerequisites, asynchronous completion, drain safety behavior, and how to verify results via list_node_groups. An agent has everything needed to call it correctly and safely.

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 the schema cannot: worker_count behaves as 0-100 in group mode versus 1-10 in legacy mode, and the target is clamped into the group's autoscaling bounds. Omission of node_group_name is described as a mode switch rather than just an optional field.

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?

Opens with a specific verb and resource ('Scale the workers of an Ankra-provisioned self-managed cluster') and enumerates the supported providers. It then cleanly separates the two modes (node-group scale vs. legacy whole-cluster scale), so an agent can immediately tell which behavior it will get.

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?

Explicitly states the condition selecting each mode: node_group_name present scales that group, absent performs the legacy whole-cluster scale, which is 'refused while any node group has autoscaling enabled - scale the group directly instead'. It also names prerequisites (cluster online, no in-progress operations) and prescribes calling list_node_groups before and after.

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.