Skip to main content
Glama

Get cluster attention summary

get_cluster_attention_summary
Read-only

Get the exact signals behind a cluster's 'Needs Attention' status badge: agent online/offline state, failing and pending resource counts with the identities of failing resources (kind, name, owning stack), the latest operation and its status, the GitOps sync health summary, and open AI insights with root causes and recommended actions. ALWAYS call this first when the user asks to fix a cluster, asks why a cluster needs attention, or asks for a cluster health/remediation plan. Works even when no cluster is selected (pass cluster_name or cluster_id); defaults to the selected cluster. All data is read from the platform database, so it works for offline clusters too. Open insights carry possibly_stale when their last scan confirmation is old - verify a stale insight against live state before acting on or reporting it.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the cluster to summarise. Optional when a cluster is selected.
cluster_nameNoExact name of the cluster to summarise. Optional when a cluster is selected.

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?

Read-only safety is already carried by readOnlyHint=true, but the description adds real behavioral context: all data comes from the platform database so it works for offline clusters, the call falls back to the selected cluster, and returned insights may carry possibly_stale when scan confirmation is old, with a directive to verify before acting. That stale-data caveat is exactly the kind of trait annotations cannot express; it stops just short of describing payload shape or absence cases (e.g. what happens with no selected cluster and no argument).

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 resource and its contents before any usage or caveat text, and every clause (offline behavior, default cluster, staleness warning) carries information. The content enumeration in the opening sentence is dense and runs long, but each listed element is one an agent needs to know is available.

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?

There is no output schema, so the description must convey return contents itself — it does so field by field, including the stale-insight flag and root-cause/recommendation subfields. Combined with the offline-data caveat and the default-cluster resolution behavior, an agent has enough to call it correctly on the first try.

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 properties are already documented as optional when a cluster is selected, so the description's 'pass cluster_name or cluster_id' and 'defaults to the selected cluster' largely restates the schema. It does not state whether the two are mutually exclusive, whether one wins if both are given, or whether an unknown name is an error — the residual gaps the schema leaves open.

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 the exact signals behind a cluster's Needs Attention status badge') and then enumerates the concrete payload: agent state, failing/pending resource counts with identities, latest operation, GitOps sync health, and open AI insights. This clearly separates it from near siblings like get_cluster_insights, get_cluster_status, or cluster_describe, which cover subsets of that surface.

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?

Gives an explicit routing rule: call this first when the user asks to fix a cluster, asks why it needs attention, or wants a health/remediation plan. It also resolves the ambiguous case of no selected cluster. What it lacks is a named alternative or a 'do not use for X' exclusion to make the boundary with get_cluster_insights/get_cluster_status fully 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.