Skip to main content
Glama
Sign In
Astronomer MCP Server

Astronomer MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_cosmic_structure

Retrieve details of a single cosmic structure, such as a galaxy or cluster, including its star systems. Use it to inspect one structure by ID for astrophysics research.

Instructions

Retrieve details of a single cosmic structure (galaxy/cluster) including its star systems.

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

Input Schema

NameRequiredDescriptionDefault
idYesCosmic Structure ID
include_star_systemsNoInclude star systems belonging to this cosmic structure

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 disclosure burden, and it delivers only the barest minimum: 'Retrieve' implies a non-mutating read. It says nothing about what happens when the ID does not exist, whether permissions or visibility rules apply, how large the response may be when star systems are embedded, or anything about error/empty behavior.

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 tight sentence with the resource and payload scope front-loaded and no filler. It is efficient, though its brevity is also the source of the missing usage guidance, so it does not reach a 5.

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

Completeness3/5

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

For a two-parameter read tool with full schema coverage and no output schema, the description covers identity and payload shape adequately. It is only minimally sufficient, however, given that no annotations exist to cover safety or failure behavior.

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 both 'id' and 'include_star_systems' documented in the schema itself. The description mentions star systems being included but adds no syntax, defaults, or edge-case meaning beyond what the schema already provides, so the baseline 3 applies.

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 names a specific verb and resource ('Retrieve details of a single cosmic structure') and scopes it to one entity, which implicitly separates it from the list-style sibling list_cosmic_structures. It also states the payload contains star systems. It stops short of explicitly naming an alternative tool, so a 4 rather than a 5.

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. The word 'single' hints that this is the by-ID detail lookup rather than a listing call, but the agent must infer that from the sibling names rather than from the description, and no prerequisites or alternatives are mentioned.

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

Deploy Server

Other Tools