Statesman MCP Server

list_cluster_groups

Retrieve all archetype cluster groups for a specific frozen cluster snapshot, optionally including member countries or cities, to inspect grouped geopolitical or urban data.

Instructions

List all archetype cluster groups belonging to a specific frozen snapshot.

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_snapshot_id": "<cluster_snapshot_id>"
    },
    "name": "list_cluster_groups"
  }
}

Input Schema

Name	Required	Description	Default
`include_members`	No	Include member countries or cities
`cluster_snapshot_id`	Yes	Cluster Snapshot ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'List' implies a read-only operation, but it says nothing about pagination, result size, ordering, or what happens when the snapshot has no groups; for a simple two-parameter read the gap is moderate rather than severe.

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 scoping constraint appears immediately. It is efficient, though its brevity contributes to the missing usage guidance.

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 two-parameter read tool with full schema coverage and no output schema, the basics are covered, including the snapshot scope. What is missing is any practical guidance on when to prefer this over get_cluster_group or list_cluster_snapshots, which an agent would need to route correctly.

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 both the required cluster_snapshot_id and the include_members boolean are already documented in the schema. The description adds no meaning beyond that, which is the baseline expectation when the schema is complete.

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 names a specific verb (List) and resource (archetype cluster groups) and scopes it to 'a specific frozen snapshot', which distinguishes it from the singular get_cluster_group sibling. It stops short of explicitly naming an alternative, but the operation and its scope are 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 when-to-use guidance, no exclusion of alternatives such as get_cluster_group, and no stated prerequisite for how to obtain the snapshot id. Only a weak implied context ('belonging to a specific frozen snapshot') hints at the workflow.

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

Deploy Server