Skip to main content
Glama

List managed node pools

list_managed_node_pools
Read-only

List the node pools of a managed Kubernetes cluster (DOKS, UKS, GKE, AKS, EKS, OVH MKS, Kapsule, Ankra Cloud Kubernetes): name, size, count, zone, autoscaling bounds, labels, taints, and provider status. For Scaleway Kapsule the listing reconciles against the provider first. 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_managed_node_pools"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the target managed cluster. Optional when a cluster is selected.
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.8/5.0
Behavior4/5

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

The 'Read-only' sentence only restates readOnlyHint=true, but the description adds a genuine behavioral trait beyond annotations: for Scaleway Kapsule the listing reconciles against the provider first, implying extra latency and a provider-side call rather than a pure cached read. That is exactly the kind of context annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose and followed by the returned-field inventory and the Kapsule caveat. The field enumeration is dense but each item adds informational value; there is no filler.

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?

With no output schema, the description usefully enumerates return fields and flags the Kapsule reconciliation behavior, which is enough to call it correctly. The only gap is the unspecified cluster-resolution rule for the optional, zero-required parameters.

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 the description adds nothing about cluster_id or cluster_name – no precedence rules or guidance for the 'optional when a cluster is selected' selection state. Baseline 3 applies since the schema carries all parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 node pools of a managed Kubernetes cluster') and enumerates the returned attributes (name, size, zone, autoscaling bounds, taints, provider status), so the agent knows exactly what it gets back. The provider list (DOKS, UKS, GKE, AKS, EKS, OVH MKS, Kapsule, Ankra) scopes it to managed clusters, which implicitly separates it from list_node_groups and list_cluster_nodes, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'managed Kubernetes cluster' hints at when this applies versus unmanaged node groups, but there is no explicit when-to-use, when-not-to-use, or named alternative. It also never says how to resolve the cluster when neither cluster_id nor cluster_name is supplied, leaving a real selection question unanswered.

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.