Skip to main content
Glama

Get cluster mesh

get_cluster_mesh
Read-only

Show one cluster mesh: its status and each member cluster's Cilium identity and status. Member status reads 'pending' before the mesh certificate authority is confirmed, 'configuring' while Cilium is being re-rendered, 'degraded' when fewer peers are connected than expected, and 'ready' once every peer is connected. Identify the mesh by mesh_id from list_cluster_meshes. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mesh_id": "<mesh_id>"
    },
    "name": "get_cluster_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
mesh_idYesThe mesh UUID.

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?

Annotations already declare readOnlyHint=true, and the description reinforces that with "Read-only." More importantly, it discloses the member status state machine — pending before the mesh CA is confirmed, configuring during Cilium re-render, degraded when peers are under-connected, ready when all peers connect — which is behavioural context an agent cannot get from annotations or schema. It omits error/not-found behaviour, keeping it short of a 5.

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?

Front-loaded with the purpose, then the status vocabulary, then the identifier source, then a read-only flag. The status enumeration is long but each state definition carries distinct information; a bulleted form would scan faster than the current run-on sentence, which is the only structural weakness.

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 must convey the return shape, and it does — mesh status and per-member Cilium identity plus status, including how to interpret each status value. For a one-parameter read tool this is complete enough to call correctly without further exploration.

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 coverage is 100% and mesh_id is documented as "The mesh UUID", so the baseline would be 3. The description adds provenance semantics, telling the agent the valid value comes from list_cluster_meshes, which is meaning beyond the schema text.

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+resource ("Show one cluster mesh") and immediately names the payload: mesh status plus each member cluster's Cilium identity and status. It is clearly distinguished from list_cluster_meshes, which is cited as the source of the identifier, so an agent won't confuse the single-fetch with the enumeration.

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?

It states the precondition for use ("Identify the mesh by mesh_id from list_cluster_meshes"), which routes the agent through the listing tool first. It does not mention adjacent alternatives such as check_cluster_mesh_readiness or make_cluster_mesh_ready, so the when-not guidance is implicit rather than explicit.

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.