Astronomer MCP Server

list_cluster_reports

List generated comparative astrophysics synthesis reports for star systems or celestial bodies; filter by status, target type, cluster snapshot ID, and pagination.

Instructions

List generated multi-phase comparative astrophysics and celestial body manifold 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: StarSystem or CelestialBody
`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.5/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 disclosure burden, and it discloses almost nothing: no mention of pagination behavior, default ordering, result scope, or what a caller gets back. "Generated" hints that only persisted reports are returned, but that is the only behavioral signal and it is ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence, so length is not the problem, but the wording is inflated with multi-syllable jargon that obscures rather than front-loads the key noun. Nothing is wasted in volume, yet clarity per word is low.

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 six-filter list tool with no annotations and no output schema, the description should say what the results are scoped to (cluster snapshots?) and how they are returned. It leaves the relationship between this tool and the report-related siblings entirely unexplained.

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 with enums and bounds, so the schema does the work. The description adds no meaning about how status, is_detailed, target_type, or cluster_snapshot_id interact as filters, which is the baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does supply a verb ("List") and a resource ("reports"), but the resource is buried in jargon like "multi-phase comparative astrophysics and celestial body manifold synthesis reports" and the word "cluster" never appears, even though the name is list_cluster_reports. It gives no basis for distinguishing this from sibling list_report_summaries or list_report_sub_reports.

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 exclusions, and no reference to any alternative such as list_report_summaries or get_cluster_report. The agent must infer the tool's role purely from the name and the schema filters.

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

Deploy Server