Statesman MCP Server

get_cluster_group

Retrieve details of a specific archetype cluster group with all member countries or cities by ID, optionally toggling member inclusion for focused geopolitics or urban analysis.

Instructions

Retrieve details of a specific archetype cluster group with all member countries or cities.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Cluster Group ID
`include_members`	No	Include member countries or cities

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

A3.6/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 burden. It does disclose the meaningful payload trait — that member countries or cities are returned with the details — which is real value beyond the schema. It says nothing about behavior on a missing/invalid ID, read-only nature, or how the include_members toggle changes the response.

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?

A single front-loaded sentence with no filler; the core action and the returned scope both appear before any optional detail.

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?

For a two-parameter read tool with no output schema and no annotations, the description conveys the essential shape of the response (group details plus members). Only error/failure behavior and the effect of setting include_members to false are unaddressed.

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%, with both 'id' and 'include_members' documented inline, so the schema already does the parameter work. The description's mention of member countries or cities loosely echoes the include_members parameter but adds no format, range, or default semantics beyond it.

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 and resource — 'Retrieve details of a specific archetype cluster group' — and adds the payload scope ('with all member countries or cities'). It implicitly contrasts with list_cluster_groups by stressing 'specific', but never names or routes away from 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is for fetching one cluster group by ID rather than enumerating groups. There is no stated prerequisite (e.g., knowing the ID), no when-not guidance, and no named alternative such as list_cluster_groups for discovery.

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

Deploy Server