Skip to main content
Glama

Get cluster details

get_cluster_details
Read-only

Get detailed information about a specific cluster by name or ID. Returns state, environment, Kubernetes version, node count, addon/stack/manifest counts, agent status, and more. Works even when no cluster is selected.

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": "get_cluster_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the cluster to look up.
cluster_nameNoExact name of the cluster to look up.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 non-obvious behavioral fact that it works with no cluster selected, plus what fields come back. It stops short of disclosing what happens when neither cluster_id nor cluster_name is supplied, or which argument wins if both are given — meaningful gaps for an identifier-optional lookup.

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 short sentences, front-loaded with the verb and identifier strategy, then the return payload, then the notable edge case. The trailing 'and more' is mild filler, but the rest earns its place.

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 compensates by enumerating the returned fields, and it flags the no-selection case — enough for a two-optional-parameter read tool. The only real shortfall is disambiguation from the crowded set of cluster describe/status/query siblings.

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 coverage is 100% and both parameters already carry their own descriptions, so the schema does the heavy lifting. The phrase 'by name or ID' mirrors the schema's two mutually-exclusive lookup keys without adding resolution rules, so baseline 3 is appropriate.

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+resource ('Get detailed information about a specific cluster') and enumerates the returned fields, which lets an agent distinguish it from list-style siblings like list_clusters. However, it does not distinguish itself from close siblings such as cluster_describe, cluster_query, get_cluster_status, or describe_resource, so an agent must guess which detail fetcher to use.

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?

The sentence 'Works even when no cluster is selected' is genuinely useful usage context — it tells the agent this tool is safe to call without prior selection state. But there is no explicit when-to-use/when-not guidance relative to the many overlapping describe/status/query siblings, leaving the agent to infer selection criteria.

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.