Statesman MCP Server

get_cluster_snapshot

Retrieve a frozen cluster snapshot by ID to inspect member groups, included countries or cities, and generated scholarly reports.

Instructions

Retrieve details of a frozen cluster snapshot including member groups and generated 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

Name	Required	Description
`id`	Yes	Cluster Snapshot ID
`include_groups`	No	Include discovered archetype cluster groups
`include_members`	No	Include countries or cities belonging to each group
`include_reports`	No	Include generated scholarly reports

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations supplied, the description carries the full burden. It hints at immutability with 'frozen snapshot' and suggests a read operation, but never states that it is read-only, whether the snapshot can expire or be deleted, what happens for an unknown ID, or how large the returned group/report set can be.

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 padding; the resource and payload contents come first. It is slightly terse in that the phrase about included sections could be read as always present rather than conditional.

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 four-parameter read tool with full schema coverage but no output schema, the description covers the basic shape but omits return-value structure and the effect of the include_* flags. Adequate, but an agent would still need the schema to call it well.

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 the four parameters are already documented in the schema, making 3 the baseline. The description mentions member groups and reports, loosely mapping to include_groups/include_members/include_reports, but never indicates that these inclusions are optional and can be switched off.

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?

The description gives a specific verb ('Retrieve') and resource ('frozen cluster snapshot') and lists the payload parts (member groups, generated reports), which cleanly separates it from list_cluster_snapshots and the narrower get_cluster_group / get_cluster_report siblings. It does not explicitly name those siblings, but the scope is unambiguous.

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?

There is no statement of when to use this tool versus list_cluster_snapshots or the per-entity getters, and no prerequisites or conditions are given. The only implicit cue is that it fetches a single snapshot by ID.

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

Deploy Server