Skip to main content
Glama

Get cluster snapshot

get_cluster_snapshot
Read-only

Get a full cluster overview in a single call. Returns: stacks with addon names and health, active namespaces, drafts in progress, and recent warning/error events. Use this as your FIRST call when you need to understand the cluster state. Prefer this over calling list_stacks + list_namespaces + get_events separately.

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

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.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so safety is covered; the description adds genuine behavioral value by disclosing that this is a composite/aggregate read that merges several data sources in one call. It stops short of covering limits, freshness of the snapshot, or what happens when a sub-resource is unavailable, but the aggregation trait is the key thing an agent needs to know.

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?

Four short sentences, front-loaded with the core action and payload contents, then routing guidance. Nothing is redundant and the sibling comparison is left to the last sentence where it belongs.

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?

Single-parameter read tool with no output schema, and the description compensates by listing the returned sections, so an agent knows what to expect. Minor gaps remain around snapshot freshness and failure behavior, but nothing essential to invoking it correctly 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?

Only one parameter (cluster_id) and schema coverage is 100%, with the schema itself pointing to list_clusters for discovery. The description adds no meaning beyond that, which is the expected baseline when the schema already fully documents the single input.

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?

Names a specific verb and resource (get cluster snapshot/overview) and enumerates exactly what comes back: stacks with addon names and health, active namespaces, drafts in progress, and warning/error events. This is clearly distinguishable from narrower siblings like get_cluster_details, list_stacks, or get_events.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use it ('FIRST call when you need to understand the cluster state') and names the exact alternatives it replaces ('Prefer this over calling list_stacks + list_namespaces + get_events separately'). Both the when and the instead-of are spelled out.

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.