Skip to main content
Glama

Add managed node pool

add_managed_node_pool
Destructive

Add a node pool to a managed Kubernetes cluster (DOKS, UKS, GKE, AKS, EKS, OVH MKS, Kapsule, Ankra Cloud Kubernetes). Requires name and size (a provider node size slug from list_managed_k8s_options with the cluster target); count defaults to 1. Optional autoscaling {enabled, min_count, max_count}, labels, and taints. The pool's nodes provision at the cloud provider in the background; the cluster must have finished provisioning.

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>",
      "size": "<size>"
    },
    "name": "add_managed_node_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesUnique node pool name.
sizeYesProvider node size slug (from list_managed_k8s_options with the cluster target).
spotNoOptional spot / preemptible capacity for the pool (AKS only). enabled defaults to true when the block is passed; max_price is the hourly cap (> 0) in the provider currency, omit it to pay up to the on-demand price.
countNoNumber of nodes in the pool. Default: 1.
labelsNoOptional Kubernetes node labels.
taintsNoOptional Kubernetes node taints, each {key, value, effect}.
cluster_idNoUUID of the target managed cluster. Optional when a cluster is selected.
autoscalingNoOptional autoscaling for the new pool; when passed, integer min_count and max_count are required (min_count >= 1, max_count >= min_count) and count must sit inside them when enabled.
cluster_nameNoExact name of the target managed cluster. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 a non-read-only, non-idempotent, destructive operation, so the safety profile is covered. The description adds real value by explaining that nodes are provisioned asynchronously at the cloud provider in the background and that the target cluster must already be provisioned, but it omits permissions requirements, failure modes (e.g., duplicate pool names), and what the call returns while provisioning is in flight.

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-loads the core action and required inputs, then covers optional blocks and prerequisites in a compact two-sentence body. The provider acronym list is dense but earns its place by defining scope; little is wasted.

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 9-parameter mutation tool with nested objects and no output schema, the description supplies the essential context: required fields, where to get the size slug, async provisioning behavior, and cluster readiness. Remaining gaps (auth/permissions, return value, conflict handling) are modest rather than blocking.

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%, including defaults for count, spot block semantics, and the autoscaling min/max constraint, so the baseline is 3. The description reinforces the size slug source and the optional label/taint/autoscaling blocks but adds no syntax or semantics the schema does not already carry.

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 node pool to a managed Kubernetes cluster") and enumerates the providers it applies to (DOKS, UKS, GKE, AKS, EKS, OVH MKS, Kapsule, Ankra). An agent can distinguish this from cluster-level creation tools immediately.

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 preconditions: name and size are required, size must come from list_managed_k8s_options with the cluster target, and the cluster must have finished provisioning before the pool can be added. It stops short of explicitly contrasting with the sibling add_node_group, so the boundary between managed and non-managed node pools is left implicit.

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.