Skip to main content
Glama

Get cluster status

get_cluster_status
Read-only

Get cluster health overview. Returns: node count (ready/not-ready), pod counts by status, resource usage percentages. Use this for a quick health check. For detailed resource lists, use get_pods/get_deployments instead.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "get_cluster_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds the concrete contents of the response, which is genuinely useful because no output schema exists. It stops short of describing how "resource usage percentages" are scoped or how recently data was sampled, which would matter for trusting a health check.

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?

Three short sentences with the return contents front-loaded, then usage guidance, then the alternative. No filler and every sentence carries information an agent needs.

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?

For a one-parameter read-only tool this is close to complete: purpose, return fields, and routing to alternatives are all present, and the missing output schema is compensated by the inline return summary. Only the vagueness of "resource usage percentages" leaves a small gap.

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 single cluster_id parameter is fully documented in the schema (UUID format, discover via list_clusters). The description adds nothing about the parameter, 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 ("Get cluster health overview") and then enumerates exactly what the read covers: node ready/not-ready counts, pod counts by status, and resource usage percentages. It also names the sibling tools it is not (get_pods/get_deployments), so an agent can distinguish it without opening any schema.

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 for a quick health check" gives an explicit use condition and the closing sentence routes detailed resource listing to get_pods/get_deployments. It does not address other plausible neighbours (get_cluster_details, get_cluster_attention_summary, get_cluster_insights), so the when-not guidance is partial rather than complete.

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.