Skip to main content
Glama

get_cluster_snapshot

Retrieve details of a frozen cluster snapshot, including member groups, subatomic particles or quantum states, and generated synthesis reports for analysis.

Instructions

Retrieve details of a frozen cluster snapshot including member groups and generated synthesis reports.

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": {
      "id": "<id>"
    },
    "name": "get_cluster_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCluster Snapshot ID
include_groupsNoInclude discovered archetype cluster groups
include_membersNoInclude subatomic particles or quantum states belonging to each group
include_reportsNoInclude generated scholarly reports

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'Frozen' hints the snapshot is immutable and this is a read, but it omits that the call can return a large nested payload when include_* flags default to true, says nothing about permission requirements, error behavior for missing/expired ids, or whether reports are pre-generated or computed on demand.

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?

A single front-loaded sentence with no filler; the resource and its contents come first. It could have used a second short clause for the when-to-use case at negligible cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read tool with no annotations and no output schema, the description identifies what comes back at a high level, which is the minimum needed. It leaves the payload shape, size implications of the default-true include flags, and failure modes undocumented.

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%, so the schema already documents all four parameters including defaults. The description corroborates include_groups and include_reports but says nothing about include_members or about the cost/size tradeoff of toggling includes, so it adds little beyond the schema.

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 ('Retrieve') and resource ('frozen cluster snapshot') plus the payload contents (member groups, synthesis reports). This distinguishes it from list_cluster_snapshots by implying a single-record fetch, though it never names a sibling explicitly.

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

Usage Guidelines2/5

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

No guidance on when to use this versus list_cluster_snapshots, get_cluster_group, or get_cluster_report, nor any prerequisite or exclusion. The only implied usage is 'fetch one snapshot by id', which the agent must infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.