Skip to main content
Glama

List cluster meshes

list_cluster_meshes
Read-only

List the organisation's Cilium cluster meshes: mesh id, name, status (pending/configuring/degraded/ready) and every member cluster with its Cilium cluster id, Cilium cluster name and per-member status. A cluster mesh joins two or more Ankra clusters into one flat pod network, so a Service in one cluster can be reached from another. Use this to see what meshes exist before creating one, or to explain a mesh's current shape. 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_meshes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the closing 'Read-only' merely restates that rather than adding new behavior. The genuinely additive part is the disclosure of the response shape and status vocabulary, which is not in any annotation or output schema. Missing behavioural detail about scope (all organisation meshes? pagination? ordering?) keeps it at adequate rather than rich.

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 field inventory is front-loaded, followed by a one-sentence conceptual gloss and then usage, which is a sensible order. The 'flat pod network / Service reachable from another cluster' explanation is useful orientation but is the one sentence that could be trimmed for an agent that only needs the call semantics.

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?

With no output schema, the description takes on the burden of describing return values and does so field by field, including the status enum domain. Combined with zero parameters and a declared read-only annotation, an agent has everything needed to call this correctly.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the schema is trivially complete. Baseline is 4 for a no-parameter tool, but the description also makes no statement about implicit scoping (organisation-scoped, unpaginated), so it does not fully earn the top of that band.

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?

The description gives a specific verb and resource ('List the organisation's Cilium cluster meshes') and enumerates exactly what comes back: mesh id, name, status values (pending/configuring/degraded/ready), and each member cluster with its Cilium cluster id, name and per-member status. It stops short of naming the closest sibling (get_cluster_mesh), so the list-vs-single distinction is left for the agent to infer from the name alone.

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?

'Use this to see what meshes exist before creating one, or to explain a mesh's current shape' supplies concrete triggering situations tied to create_cluster_mesh. There is no explicit exclusion such as 'use get_cluster_mesh when you already know the mesh id', which would have made routing between the two siblings unambiguous.

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.