Statesman MCP Server

list_cluster_reports

Retrieve generated multi-phase comparative geopolitics and urban power synthesis reports; filter by status, target country or city, detail level, or cluster snapshot to find relevant analyses.

Instructions

List generated multi-phase comparative geopolitics and urban power synthesis reports.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cluster_reports"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Pagination limit
`offset`	No	Pagination offset
`status`	No	Filter by report generation status
`is_detailed`	No	Filter by whether report is a 3-phase detailed deep synthesis
`target_type`	No	Filter by target entity type: Country or City
`cluster_snapshot_id`	No	Filter reports for a specific cluster snapshot ID

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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state that this is a read-only operation, what permissions may be required, how results are ordered, whether pagination behavior differs from schema defaults, or what the response contains. It only clarifies that the listed items are generated multi-phase synthesis reports.

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?

The definition is a single front-loaded sentence with no wasted clauses or repetition. The qualifier 'multi-phase comparative geopolitics and urban power synthesis' is verbose but still compact enough to serve as a resource description.

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?

There is no output schema and no annotations, so the description should provide more context about what is returned, ordering, permissions, and any usage constraints. For a six-parameter list tool, the current description gives purpose but leaves significant operational gaps.

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%, and all six parameters are documented in the schema with defaults, enums, and constraints. The description adds no additional parameter meaning, so the baseline of 3 is appropriate.

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, 'List', and a specific resource, 'generated multi-phase comparative geopolitics and urban power synthesis reports'. It is distinguishable from get_cluster_report because it lists rather than retrieves a single report, but it does not explicitly contrast with nearby siblings such as list_report_sub_reports or list_report_summaries.

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 or when-not-to-use guidance, and no alternatives are named. The listing intent is only implied by the verb and by sibling tool names, which is insufficient for an agent choosing among many list tools.

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

Deploy Server