Statesman MCP Server

create_cluster_report

Initiates a two-phase map-reduce synthesis report from a frozen cluster snapshot and prompt, enabling comparative geopolitical analysis.

Instructions

Initiate a 2-Phase Map-Reduce synthesis report on a frozen cluster 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>",
      "prompt": "<prompt>"
    },
    "name": "create_cluster_report"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	Yes	Scholarly geopolitical investigation prompt (e.g. 'Analyze cross-continental archetypes of maritime gateway states and naval infrastructure.')
`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?

With no annotations, the description carries the full behavioral burden. It does disclose meaningful behavior by naming a '2-Phase Map-Reduce' synthesis process and a 'frozen' snapshot, but it omits whether initiation is asynchronous, what is returned, whether a job must be polled, and any permission or cost considerations.

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?

The definition is a single front-loaded sentence with no filler. Every phrase contributes to identifying the action, process model, and input context.

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

Completeness2/5

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

For a report-creation tool with no output schema and no annotations, the definition is incomplete. It does not explain the return value or job lifecycle, how to check status, whether the call blocks, or what happens after the report is initiated.

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 schema already documents both parameters. The description adds only slight meaning by linking 'cluster_snapshot_id' to a frozen snapshot and 'prompt' to the synthesis report; it does not clarify expected prompt structure or snapshot state requirements 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?

The description states a specific verb ('Initiate') and resource ('2-Phase Map-Reduce synthesis report') scoped to a 'frozen cluster snapshot.' It is distinguishable from list/get/delete cluster report siblings, but it does not explicitly differentiate itself from create_cluster_snapshot or generate_deep_synthesis.

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 explicit when-to-use guidance, no when-not-to-use guidance, and no named alternatives. The phrase 'on a frozen cluster snapshot' hints at a prerequisite, but the description never states that a snapshot must already exist or how this differs from other report-generation tools.

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

Deploy Server