Skip to main content
Glama

Add node group

add_node_group
Destructive

Add a new worker node group to an Ankra-provisioned self-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, Ankra Cloud, Proxmox VE, or HPE Morpheus): creates count workers (default 1) of the given instance_type with optional labels, taints, and autoscaling settings. Instance types are provider-specific (e.g. 'cx23' on Hetzner, 'px-medium' on Proxmox VE; for HPE Morpheus pass the numeric service-plan id as a string). Group names are lowercase alphanumeric with hyphens and must not already exist. Works on a running or stopped cluster; new workers provision in the background.

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": {
      "name": "<name>",
      "instance_type": "<instance_type>"
    },
    "name": "add_node_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesUnique node group name (lowercase alphanumeric with hyphens).
zoneNoUpCloud multi-zone clusters only: pin every node of the group to one zone of the cluster's pool (e.g. 'fi-hel2'). Omit to spread the group across the pool.
countNoNumber of workers to create. Default: 1.
labelsNoOptional Kubernetes node labels.
taintsNoOptional Kubernetes node taints, each {key, value, effect}.
disk_tierNoAnkra Cloud only: storage tier of the root disk of every server the group creates, scale-ups included. Omit it for the zone's default tier. local-nvme puts the disk on the node's own fast disks (the right choice for CI nodes); standard, maxiops and hdd are the zone's Ankra Storage tiers. Refused on other providers.
user_dataNoOVH only: opaque cloud-init user data applied verbatim at first boot by every instance the group ever creates, replacements included. Ankra sends no cloud-init of its own, so the document applies unmerged - use it for provision-time disk layouts (e.g. growpart mode off + sgdisk to carve a LUKS partition). Max 65535 bytes.
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
autoscalingNoOptional autoscaling settings: {enabled, min_count, max_count}. Bounds default to 1 and 100. min_count 0 (scale-to-zero) is allowed only when Ankra can size the group's instance_type, and is refused naming the instance type when it cannot. Enabling requires a recent cluster agent. Not available on Proxmox VE or HPE Morpheus clusters: the Cluster Autoscaler cannot add or remove their workers, so size the group with its count instead.
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.
instance_typeYesProvider instance type for the group's workers (list_instance_types / list_proxmox_options / list_morpheus_options). It must be in stock at the cluster's location: call list_instance_types with cluster_id and pick an available type that fits the workloads' requests - an out-of-stock type is refused before the card is raised, naming in-stock types of at least its size.
swap_behaviorNoKubelet swap behaviour of those nodes. LimitedSwap is the only value and the default when swap_gibibytes is set; refused without swap_gibibytes.
disk_gibibytesNoAnkra Cloud only: root disk size in GiB of every server the group creates, scale-ups included. Omit it for the plan's included disk. Refused on other providers.
swap_gibibytesNoOVH k3s clusters on Kubernetes v1.36 or newer only: size in GiB of the encrypted swap every worker the group creates is built with, replacements and autoscaler scale-ups included. Refused on kubeadm, on older releases and on other providers. A node that cannot take swap still joins, without it, and list_node_groups names it in workers_without_swap; a node the platform has no answer from is in workers_swap_unknown, and may have swap.
availability_zoneNoOVH 3-AZ regions only: pin every node of the group to one availability zone (e.g. 'eu-west-par-b'). Omit to spread the group across the cluster's zones. Pin when the group runs zonal storage - an OVH High Speed volume cannot attach from another zone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / count / minimum
      Previous value: -0New value: +1
  2. Changed1 schema field changed
    • changedInput schema / properties / autoscaling / description
      Previous value: -"Optional autoscaling settings: {enabled, min_count, max_count}. Bounds default to 1 and 100. min_count 0 (scale-to-zero) is allowed only when Ankra can size the group's instance_type, and is refused naming the instance type when it cannot. Enabling requires a recent cluster agent."New value: +"Optional autoscaling settings: {enabled, min_count, max_count}. Bounds default to 1 and 100. min_count 0 (scale-to-zero) is allowed only when Ankra can size the group's instance_type, and is refused naming the instance type when it cannot. Enabling requires a recent cluster agent. Not available on Proxmox VE or HPE Morpheus clusters: the Cluster Autoscaler cannot add or remove their workers, so size the group with its count instead."
  3. Changed2 schema fields changed
    • addedInput schema / properties / swap_behavior
      Added value: +{
      +  "description": "Kubelet swap behaviour of those nodes. LimitedSwap is the only value and the default when swap_gibibytes is set; refused without swap_gibibytes.",
      +  "enum": [
      +    "LimitedSwap"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / swap_gibibytes
      Added value: +{
      +  "description": "OVH k3s clusters on Kubernetes v1.36 or newer only: size in GiB of the encrypted swap every worker the group creates is built with, replacements and autoscaler scale-ups included. Refused on kubeadm, on older releases and on other providers. A node that cannot take swap still joins, without it, and list_node_groups names it in workers_without_swap; a node the platform has no answer from is in workers_swap_unknown, and may have swap.",
      +  "maximum": 1024,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / instance_type / description
      Previous value: -"Provider instance type for the group's workers (list_instance_types / list_proxmox_options / list_morpheus_options)."New value: +"Provider instance type for the group's workers (list_instance_types / list_proxmox_options / list_morpheus_options). It must be in stock at the cluster's location: call list_instance_types with cluster_id and pick an available type that fits the workloads' requests - an out-of-stock type is refused before the card is raised, naming in-stock types of at least its size."
  5. Changed2 schema fields changed
    • addedInput schema / properties / disk_gibibytes
      Added value: +{
      +  "description": "Ankra Cloud only: root disk size in GiB of every server the group creates, scale-ups included. Omit it for the plan's included disk. Refused on other providers.",
      +  "maximum": 4096,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / disk_tier
      Added value: +{
      +  "description": "Ankra Cloud only: storage tier of the root disk of every server the group creates, scale-ups included. Omit it for the zone's default tier. local-nvme puts the disk on the node's own fast disks (the right choice for CI nodes); standard, maxiops and hdd are the zone's Ankra Storage tiers. Refused on other providers.",
      +  "enum": [
      +    "local-nvme",
      +    "standard",
      +    "maxiops",
      +    "hdd"
      +  ],
      +  "type": "string"
      +}
  6. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation profile is known. The description adds genuine context beyond that: name uniqueness enforcement, background provisioning, refusals raised before the card is charged, and provider-gated parameters. However, it does not say what happens to existing groups or what the call returns, so it is solid but not exhaustive.

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 the core action and provider scope, then constraints, with no filler sentences. The single dense paragraph packs many provider-specific caveats into one long sentence, which slightly hurts scannability but every clause carries 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 15-parameter mutation with no output schema, the description covers provider gating, name rules, async provisioning, and autoscaling limits well. The notable gap is the return value and how to confirm the background provisioning succeeded, which an agent would need before verifying the call.

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 coverage is 100%, so the baseline is 3, and the description largely restates schema content (default count of 1, name format, provider-specific instance types, Morpheus numeric service-plan id as a string). The cross-parameter rules it surfaces (swap_behavior refused without swap_gibibytes, min_count 0 only when the instance type can be sized) are the main added meaning, but they are already spelled out in the schema descriptions.

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?

States a specific verb and resource ('Add a new worker node group') and narrows the scope to Ankra-provisioned self-managed clusters, listing the supported providers. The 'self-managed' framing implicitly separates it from the managed node pool siblings, so an agent can pick it without opening the schema.

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?

Gives concrete usage conditions: works on a running or stopped cluster, new workers provision in the background, and instance_type must be in stock at the cluster's location with a pointer to list_instance_types / list_proxmox_options / list_morpheus_options. It also carves out exclusions (autoscaling unavailable on Proxmox VE and HPE Morpheus). It never explicitly contrasts with add_managed_node_pool, so it stops short of full alternative 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.