Skip to main content
Glama
Sign In
Astronomer MCP Server

Astronomer MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_star_systems

List and filter star systems by name, theme, cosmic structure, celestial body counts, and vector embedding status to support astrophysics research.

Instructions

List and filter star systems with astrophysical themes, celestial body counts, and vector embedding status.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch star system name or description substring
limitNoPagination limit (default: 50)
themeNoFilter star systems containing thematic tag (e.g. 'binary', 'neutron star', 'habitable zone')
offsetNoPagination offset (default: 0)
embeddedNoFilter by whether vector embedding has been generated
cosmic_structureNoFilter by cosmic structure name substring (e.g. 'Milky Way')
include_embeddingNoInclude raw 1024-float vector array
cosmic_structure_idNoFilter by cosmic structure ID
include_celestial_bodiesNoInclude associated celestial bodies (planets/moons)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 full behavioral burden. It does establish that this is a read-only listing and names the categories of data exposed, but it omits ordering guarantees, what a default result looks like, and any warning that include_embedding pulls a raw 1024-float array per record — a meaningful cost the agent only discovers from the schema.

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; the verb and resource come first and the qualifiers follow. It is efficient, though the trailing list of attributes is slightly vague about whether these are filter dimensions or returned fields.

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 nine-parameter, zero-required filter tool with no output schema and no annotations, the description is minimally adequate. It says what is listed but not how results are shaped or ordered, and gives no indication that the two include_* flags materially expand payload size — the main behavioral risk in calling this tool.

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%, including defaults, bounds, and examples for theme and cosmic_structure, so the schema does the heavy lifting and baseline 3 applies. The description's mention of themes, celestial body counts, and embedding status loosely maps to theme, include_celestial_bodies, and embedded, but adds no filtering syntax or interaction details beyond the schema.

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?

States a specific verb and resource ("List and filter star systems") and adds what is surfaced: astrophysical themes, celestial body counts, and vector embedding status. An agent can distinguish it from mutation siblings like create_star_system or populate_star_systems_bulk by the list/filter framing, though it never explicitly contrasts with get_star_system or list_celestial_bodies.

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: nothing tells the agent to prefer this over get_star_system for a single record, or over list_celestial_bodies when the goal is the child records. The only implied usage comes from the verb "List and filter," with no exclusions or prerequisites stated.

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