Skip to main content
Glama
Sign In
Astronomer MCP Server

Astronomer MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search

Find star systems and celestial bodies across catalogs using semantic or keyword queries, with entity-type filters and configurable result limits.

Instructions

Unified cross-catalog semantic or keyword search across star systems and celestial bodies in the Astronomer comparative astrophysics manifold.

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": {
      "q": "<q>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query text (e.g. 'tidally locked habitable zone exoplanet', 'millisecond pulsar neutron star')
modeNoSearch mode: semantic (pgvector cosine similarity), keyword (text matching), or autoauto
limitNoMaximum number of results to return (1-100)
target_typeNoFilter search results by entity type: all, star_system, or celestial_bodyall

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 burden of behavioral disclosure. It states the search mechanisms but says nothing about ranking/result ordering, whether results combine both entity types, authentication needs, or result shape - all of which matter for an unannotated read tool with no output 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 the action and scope stated first. The trailing phrase 'in the Astronomer comparative astrophysics manifold' is framing rather than information the agent needs, but overall there is no bloat.

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?

With four fully documented parameters, a clear default for mode (auto), and no output schema, the minimum needed to call the tool is covered. What is missing is what comes back - result shape, ranking, and how semantic vs keyword differ in outcome - which the description could reasonably have sketched given the absence of an output schema.

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 enum values and defaults for mode, limit, and target_type, so the schema does the explanatory work. The description adds only that the search spans two catalogs, which slightly extends the 'all' target_type meaning but contributes no new parameter detail.

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 ('search') plus resource scope ('star systems and celestial bodies') and names the two supported mechanisms (semantic or keyword). It is clear what the tool does, though it never contrasts itself with siblings like list_celestial_bodies or find_counterparts that could also surface entities.

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 or when-not-to-use guidance, and no alternative is named. 'Cross-catalog' hints at broad discovery rather than enumerated listing, but an agent must infer that on its own when deciding between this and the list_* or get_* siblings.

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