Skip to main content
Glama

List clusters

list_clusters
Read-only

List all clusters in the user's organisation with their state, environment, Kubernetes version, and resource counts. Use this when the user asks how many clusters they have, wants to see all their clusters, or needs to find a specific cluster. Works even when no cluster is selected. Archived (parked) clusters are excluded from unfiltered listings; include them by filtering state 'archived' or by looking a cluster up by name.

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_clusters"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFilter clusters by name prefix (case-insensitive).
stateNoFilter by cluster state(s), e.g. ['running', 'online', 'stopped']. Use 'archived' to list parked clusters.
environmentNoFilter by environment label.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real behavioral detail beyond that: archived/parked clusters are silently excluded from unfiltered listings and how to surface them. It does not mention result limits, pagination, or ordering, which are the remaining unknowns for a fleet listing.

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?

Three front-loaded sentences: purpose and payload first, selection guidance second, the archived caveat last. Wording is tight, though 'wants to see all their clusters' and 'needs to find a specific cluster' overlap slightly with the name-filter capability already described.

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?

There is no output schema, but the description names the key returned fields (state, environment, Kubernetes version, resource counts), which compensates. For a zero-required-parameter read tool with full schema coverage, the only meaningful omission is pagination or result-size behavior.

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 schema already documents the name prefix, state array, and 'archived' semantics, so the description's mention of filtering by state 'archived' or looking up by name largely restates it. The list of returned attributes hints at what the filters interact with but adds no new parameter meaning, 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?

States a specific verb and resource ('List all clusters in the user's organisation') plus the attributes returned (state, environment, Kubernetes version, resource counts). The clause 'Works even when no cluster is selected' separates it from cluster-scoped siblings such as get_cluster_details or cluster_describe.

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?

Explicitly names the intents that select this tool: counting clusters, viewing all clusters, or locating a specific one, and clarifies it works with no cluster selected. It gives a clear include/exclude rule for archived clusters but never names competing siblings such as cluster_search or cluster_query, so the routing guidance is incomplete.

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.