Skip to main content
Glama

List node groups

list_node_groups
Read-only

List the day-2 topology of an Ankra-provisioned self-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, Ankra Cloud, Proxmox VE, or HPE Morpheus) in one call: every worker node group (instance type, node count, scaling bounds, labels, taints, autoscaling settings), the control plane (count, instance type, supported counts, whether it can be changed right now and why not), and the legacy whole-cluster worker count. Call this before scale_workers, add_node_group, update_node_group, delete_node_group, or change_control_plane. Not available for imported or managed-Kubernetes clusters. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description's "Read-only" is consistent with that rather than contradictory. Beyond the annotation it adds real behavioral context: it discloses the full response content, notes the tool surfaces whether the control plane "can be changed right now and why not", and flags an availability constraint (no imported or managed-K8s clusters). It stops short of mentioning pagination or any size/rate limits, so it is not fully complete.

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?

The purpose and scope are front-loaded, and the follow-up sentences handle sequencing, exclusions and read-only status without filler. The middle enumeration is dense but every item (scaling bounds, taints, supported control-plane counts) is information the agent needs to know it can get before mutating.

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 two-optional-parameter read tool with no output schema, the description carries the necessary weight by describing the returned fields, the precondition ordering relative to mutation tools, the cluster-type restriction, and the safety profile. Nothing an agent needs in order to decide to call it or to interpret the result is missing.

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% and both parameters (cluster_id UUID, cluster_name exact name, both optional when a cluster is selected) are documented in the schema itself. The description adds no interpretation of these selector parameters, so the baseline 3 applies.

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 ("List the day-2 topology of an Ankra-provisioned self-managed cluster") and then enumerates exactly what data comes back: worker node groups with instance type, counts, scaling bounds, labels, taints and autoscaling, plus control-plane state and the legacy worker count. That level of detail distinguishes it from nearby read tools such as list_cluster_nodes, get_nodes or list_managed_node_pools without the agent needing to open any schema.

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 an explicit trigger sequence ("Call this before scale_workers, add_node_group, update_node_group, delete_node_group, or change_control_plane") and an explicit exclusion ("Not available for imported or managed-Kubernetes clusters"). Both when-to-use and when-not-to-use are covered, which is the top of the scale.

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.