Astronomer MCP Server

list_cluster_snapshots

List frozen archetype cluster snapshots with pagination and optional filtering by StarSystem or CelestialBody, plus optional cluster groups for each snapshot.

Instructions

List frozen archetype cluster snapshots.

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

Input Schema

Name	Required	Description
`limit`	No	Pagination limit
`offset`	No	Pagination offset
`target_type`	No	Filter by target entity type: StarSystem or CelestialBody
`include_groups`	No	Include cluster groups for each snapshot

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden: it never states that this is non-mutating, whether snapshots are immutable, how pagination works, or whether authentication/limits apply. The single word 'frozen' hints at immutability but is not developed into actionable behavior.

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?

One short, front-loaded sentence with no filler, but it is under-specified rather than efficiently concise. Nothing is stated before the resource name that would orient the agent faster.

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 tool with four parameters, no annotations, and no output schema, the definition should explain filtering, pagination, and the return shape. None of that is present, leaving the agent dependent entirely on the schema and guesses about semantics.

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%, with each of the four parameters (limit, offset, target_type, include_groups) documented in the schema, so the baseline is 3. The description adds no extra meaning about filtering by target type or the effect of include_groups.

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 gives a specific verb (List) and a specific resource (frozen archetype cluster snapshots), so an agent can tell this is a read/enumeration tool. It does not, however, distinguish it from close siblings such as list_cluster_groups or get_cluster_snapshot, and 'frozen archetype' is unexplained jargon.

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 guidance on when to use this list versus get_cluster_snapshot or list_cluster_groups, and no statement of prerequisites or filtering scenarios. The only hint of usage is the word 'frozen', which is not tied to any condition.

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

Deploy Server