Skip to main content
Glama

List cluster nodes

list_cluster_nodes
Read-only

List the provisioned VM nodes of an Ankra-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, Ankra Cloud, Proxmox, or HPE Morpheus): every control-plane and worker server plus the cluster's single bastion/gateway node, with id, name, role, node group, instance type, observed Kubernetes version, location, lifecycle state, IPs, and the cloud provider's live status/power state when available. Use this before restart_node to find the exact node to target - each node's 'is_bastion_or_gateway' flag identifies the bastion/gateway even though its name varies by cluster. The per-node kubernetes_version identifies which nodes sit on the wrong side of a kubelet version skew. Deleted machine rows (workers a scale down or a stop removed) are left out unless include_deleted is true; deleted_nodes_omitted says how many were. Not available for imported (non-Ankra-provisioned) 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_cluster_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the cluster to list nodes for. Optional when a cluster is selected.
cluster_nameNoExact name of the cluster to list nodes for. Optional when a cluster is selected.
include_deletedNoAlso list deleted machine rows, marked is_deleted. Defaults to false: only the current machines are listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_deleted
      Added value: +{
      +  "description": "Also list deleted machine rows, marked is_deleted. Defaults to false: only the current machines are listed.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description adds substantial behavioral context beyond that: deleted machine rows are omitted by default, deleted_nodes_omitted reports how many were hidden, live provider status/power state is included when available, and the tool is unavailable for certain cluster types.

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 description is front-loaded with the core purpose, then adds usage, caveats, and field details in a single dense paragraph. It is informative and mostly efficient, though the long list of providers and returned fields could be tightened.

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?

Given there is no output schema, the description supplies the returned fields, node-role details, bastion identification, version-skew relevance, deleted-node filtering, and availability exclusions. This is complete enough for an agent to call and interpret the tool correctly.

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 description coverage is 100%, so the schema already documents all three parameters. The description adds useful meaning about include_deleted: deleted rows are excluded unless true, and the response includes a deleted_nodes_omitted count.

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: list the provisioned VM nodes of an Ankra-managed cluster. It also specifies the scope (control-plane, worker, and bastion/gateway nodes) and lists the returned fields, making the tool's purpose unmistakable.

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 says to use this before restart_node to identify the exact target node, and clearly states it is not available for imported or managed-Kubernetes clusters. It also explains the include_deleted behavior, giving both usage conditions and exclusions.

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.