Astronomer MCP Server

get_report_sub_report

Retrieve a single Phase 2 batch analysis by cluster sub-report ID to inspect its results for astrophysics research.

Instructions

Retrieve a single Phase 2 batch analysis.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Cluster Sub-Report 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?

With no annotations, the description carries the full burden, and it discloses almost nothing: 'Retrieve' weakly implies read-only, but there is no statement about permissions, error behavior for an unknown ID, or what the returned analysis contains. For a tool with zero annotation coverage this is a substantial gap.

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 front-loaded sentence with no padding, which is structurally fine. However, the one sentence it spends is on ambiguous jargon ('Phase 2 batch analysis') rather than a useful disambiguator, so the brevity does not earn much.

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?

A one-parameter read tool is simple, but with no annotations and no output schema the description should at least indicate what a sub-report contains or how it relates to the parent report. As written, an agent knows only that it retrieves something by ID.

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 coverage is 100% and the single 'id' parameter is documented in the schema as 'Cluster Sub-Report ID', so the baseline is 3. The description adds no meaning beyond that and in fact introduces a different label ('Phase 2 batch analysis') that does not map cleanly onto the schema's identifier.

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 gives a verb ('Retrieve') and a scope ('a single'), but the resource is named 'Phase 2 batch analysis' while the tool name says 'report sub report' and the schema parameter says 'Cluster Sub-Report ID'. The agent can infer it fetches one sub-report, but the terminology is inconsistent enough that it cannot be fully sure what object it is getting.

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 prerequisites, and no mention of alternatives. Siblings such as get_cluster_report, get_report_summary, and list_cluster_reports plausibly overlap, yet the description gives no signal for choosing between them.

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

Deploy Server