Skip to main content
Glama
Sign In
Statesman MCP Server

Statesman MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_report_sub_reports

Lists all Phase 2 intermediate batch analyses for a specified detailed synthesis report, helping retrieve sub-reports by cluster report ID.

Instructions

List all Phase 2 intermediate batch analyses belonging to a detailed synthesis report.

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_report_id": "<cluster_report_id>"
    },
    "name": "list_report_sub_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_report_idYesCluster Report ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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. 'List' implies a read-only operation, but it does not state that there are no side effects, whether results are paginated, how permissions are handled, or what happens with an invalid cluster_report_id.

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 wasted wording. The object being listed and its owning report are both stated immediately.

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 simple one-parameter list tool, the description identifies the resource and scope but omits return shape, ordering, pagination behavior, and any prerequisites. With no output schema present, a little more guidance would be useful.

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 the single required parameter is documented as 'Cluster Report ID'. The phrase 'belonging to a detailed synthesis report' loosely ties the parameter to the report scope but adds no syntax, format, or constraint detail 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?

States a specific verb ('List') and resource ('Phase 2 intermediate batch analyses') scoped to a detailed synthesis report. This clearly distinguishes it from the singular get_report_sub_report sibling, though the domain jargon 'Phase 2 intermediate batch analyses' assumes prior context.

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 implied: retrieve all sub-reports belonging to a given cluster report. The description gives no explicit when-to-use guidance, no exclusions, and does not name an alternative such as get_report_sub_report for a single item.

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

Deploy Server

Other Tools