Astronomer MCP Server

get_cluster_snapshot

Retrieve a frozen cluster snapshot by ID, including member groups, star systems, and generated scholarly reports, so agents can run comparative astrophysics research on stored cluster data.

Instructions

Retrieve details of a frozen cluster snapshot including member groups and generated reports.

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

Input Schema

Name	Required	Description
`id`	Yes	Cluster Snapshot ID
`include_groups`	No	Include discovered archetype cluster groups
`include_members`	No	Include star systems or celestial bodies belonging to each group
`include_reports`	No	Include generated scholarly reports

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the behavioral burden; "Retrieve" does signal a non-mutating read, and "frozen" hints that the snapshot is immutable. It stops short of disclosing permission requirements, behavior on an unknown/invalid ID, or how the include_* switches change payload size and cost.

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 filler, and every phrase (frozen, member groups, generated reports) carries content. It is efficient, though its brevity contributes to the missing usage context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter read tool with no output schema and no nested objects, the description covers identity and the main returned components. Missing pieces are how to source the snapshot ID and what happens on failure, which are modest gaps rather than blockers.

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%, so each parameter is already documented, making the baseline 3. The description echoes two of the optional toggles (member groups, generated reports) but adds no semantics beyond the schema and omits include_members entirely.

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 ("Retrieve") with a precisely scoped resource ("details of a frozen cluster snapshot") and names the payload composition (member groups, generated reports). This distinguishes it from sibling list_cluster_snapshots (plural listing) and from get_cluster_group/get_cluster_report (single sub-resource views), though it never states those contrasts explicitly.

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 only implied: an agent infers this is the single-snapshot lookup tool, presumably by ID. The description never says when to prefer it over list_cluster_snapshots or the narrower get_cluster_group/get_cluster_report calls, nor does it mention that an ID must be obtained elsewhere first.

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

Deploy Server