Skip to main content
Glama

Get cluster insights

get_cluster_insights
Read-only

Read the platform's own AI health diagnoses for this cluster (the cluster_ai_insights store the background analyzer maintains): open and recent issues with severity, confidence, root-cause analysis, recommended actions and remediation commands, plus recurrence_count and previous_resolutions - what was tried before for the SAME recurring issue and whether it worked. ALWAYS check this at the start of troubleshooting: if the issue recurs, propose a DIFFERENT approach than the failed previous resolutions. Read-only. Optional filters: status (default open+acknowledged), severity, include_resolved to include the resolution history of closed issues. 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

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax insights to return (default 10).
statusNoStatuses to include (default: open and acknowledged).
severityNoOnly insights at this severity.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
include_resolvedNoShorthand: also include resolved/auto_resolved issues (their previous_resolutions carry what fixed them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Read-only is already in annotations, but the description adds substantial behavior the annotations do not cover: the possibly_stale flag and the obligation to verify stale insights against live state, the default filter of open+acknowledged, and the semantic meaning of previous_resolutions as prior attempts for the SAME recurring issue. These are decision-shaping facts an agent could not derive from the schema or annotations.

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 core action and the troubleshooting directive, and every clause carries information. However it is a single dense em-dash-chained passage, and the record-contents enumeration plus the stale warning could be split or trimmed for faster scanning.

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 compensates by describing what an insight record contains (severity, confidence, root cause, recommended actions, remediation commands, recurrence_count, previous_resolutions) and how to interpret staleness. For a 5-parameter read-only diagnostic tool, nothing material is missing.

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%, so every parameter is already documented with defaults and enum meanings. The description restates status default, severity and include_resolved briefly but adds little syntax or semantics beyond the schema. Baseline 3 applies since the schema carries the parameter burden.

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: 'Read the platform's own AI health diagnoses for this cluster', and immediately grounds it in the underlying store (cluster_ai_insights maintained by a background analyzer). It enumerates the record contents (severity, confidence, root-cause, remediation commands, recurrence_count, previous_resolutions), which clearly separates it from generic siblings like cluster_describe or get_cluster_status.

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 directive: 'ALWAYS check this at the start of troubleshooting', plus a follow-up rule to propose a DIFFERENT approach when an issue recurs, and to verify stale insights against live state before acting. Strong context, but it never names a competing sibling (e.g. get_cluster_attention_summary, get_events) or states when NOT to call it, so routing among similar diagnostic tools is left to inference.

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.