Astronomer MCP Server

create_cluster_report

Initiates a two-phase Map-Reduce synthesis report on a frozen astrophysics cluster snapshot from a scholarly investigation prompt, enabling comparative research and monograph generation.

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 astrophysical investigation prompt (e.g. 'Analyze cross-galactic archetypes of red dwarf planetary systems and habitable zones.')
`cluster_snapshot_id`	Yes	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 exist, so the description carries the full behavioral burden. It discloses that the operation is a multi-phase synthesis over a frozen snapshot (implying a costly, long-running job), but says nothing about whether it is asynchronous, what identifier or job handle comes back, whether repeat calls create duplicate reports, or what permissions are needed.

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?

A single front-loaded sentence with no padding; the action, the artifact, and the input precondition all appear immediately. The compression costs some clarity around the "2-Phase Map-Reduce" term, but nothing is wasted.

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?

This is a job-initiating, non-trivial tool with no annotations and no output schema, yet the description never explains what the call returns, how progress is tracked, or how the resulting report relates to siblings like get_cluster_report or get_job_status. For a tool of this complexity the definition leaves the agent guessing about the post-call workflow.

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%, so both parameters are already documented, including the prompt's scholarly-investigation framing and the snapshot ID's integer bounds. The description adds only a conceptual link (prompt drives the synthesis, snapshot is frozen), which matches the baseline 3 rather than exceeding it.

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 pairs a specific verb ("Initiate") with a specific resource (a synthesis report over a cluster snapshot), and the phrase "frozen cluster snapshot" implicitly separates it from snapshot-creation siblings and from reporting readers like get_cluster_report. It does not explicitly name a sibling, and "2-Phase Map-Reduce" is unexplained jargon, keeping it out of 5 territory.

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 routing to alternatives such as generate_deep_synthesis or get_cluster_report. The only usable cue is the word "frozen", which hints the snapshot must already exist in a finalized state, but the agent must infer that prerequisite.

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

Deploy Server