Skip to main content
Glama

Get cluster agent status

get_cluster_agent_status
Read-only

The Ankra agent's own status on a cluster (the twin of ankra cluster agent status): whether it is online, its version against the latest release, whether an upgrade is available or in progress, whether automatic upgrades are disabled, when it last checked in, and its security standing for the NATS least-privilege cutover - nats_grant (scoped or legacy, null when not recorded yet), nats_scoped_inbox (whether it advertises the capability, null when it never identified) and security_upgrade_required (true means upgrade it with upgrade_cluster_agent; null means not known yet, never no). Use this when a cluster reads as offline, a feature needs a newer agent, or a security upgrade notice is shown. Read-only.

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

Input Schema

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

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?

Beyond readOnlyHint, it discloses the unusual null semantics that would otherwise be misread: nats_grant is null when not recorded, nats_scoped_inbox is null when never identified, and security_upgrade_required null means 'not known yet, never no'. That last clarification materially prevents an agent from treating an absent value as a clean bill of health. The trailing 'Read-only' merely repeats the annotation and adds nothing.

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?

Purpose is front-loaded and no sentence is filler; the field enumeration is dense but each item is genuinely required for interpretation. The main weakness is that the entire field list is a single run-on sentence, which makes the security-related nulls harder to isolate than a structured list would.

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 carry the return contract, and it does: every meaningful field plus how to interpret nullable security states is spelled out. For a two-optional-parameter read tool with annotations covering safety, nothing an agent needs to call or interpret it 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 cluster_id and cluster_name are already documented, and the description adds nothing about their resolution priority or the 'a cluster is selected' default case. Baseline 3 applies where 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 subject and resource ('The Ankra agent's own status on a cluster') and enumerates exactly which fields it returns: online state, version vs latest release, upgrade availability, auto-upgrade disabled, last check-in, and NATS security standing. Naming the CLI twin (`ankra cluster agent status`) lets an agent separate it from the broader get_cluster_status or get_cluster_details siblings.

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 three concrete triggers: a cluster reading as offline, a feature needing a newer agent, or a security upgrade notice. It also routes remediation by naming upgrade_cluster_agent when security_upgrade_required is true. It stops short of an explicit exclusion (e.g. 'do not use for general cluster health, use get_cluster_status'), so the boundary with siblings is inferable but not stated.

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.