Skip to main content
Glama
Sign In
ProgramComputer

NASA MCP Server

by ProgramComputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

NASA Exoplanet Archive query

nasa_exoplanet
Read-onlyIdempotent

Query NASA Exoplanet Archive TAP service with ADQL to filter, sort, and export exoplanet data from tables like ps, pscomppars, cumulative, and toi.

Instructions

Query the NASA Exoplanet Archive through its TAP service (ADQL). Tables use current TAP names such as ps, pscomppars, cumulative and toi.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows (1-1000).
orderNoADQL ORDER BY expression, e.g. pl_name.
tableYesTAP table, e.g. ps (Planetary Systems), pscomppars, cumulative (Kepler KOI), toi.
whereNoADQL WHERE condition, e.g. disc_year > 2020 and discoverymethod = 'Transit'.
formatNoResult format.json
selectNoColumns to return (ADQL select list). Defaults to *.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / format
      Added value: +{
+  "default": "json",
+  "description": "Result format.",
+  "enum": [
+    "json",
+    "csv"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / limit / default
      Added value: +100
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results"New value: +"Maximum rows (1-1000)."
    • addedInput schema / properties / limit / maximum
      Added value: +1000
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / order / description
      Previous value: -"Ordering of results"New value: +"ADQL ORDER BY expression, e.g. pl_name."
    • addedInput schema / properties / order / minLength
      Added value: +1
    • changedInput schema / properties / select / description
      Previous value: -"Columns to return"New value: +"Columns to return (ADQL select list). Defaults to *."
    • addedInput schema / properties / select / minLength
      Added value: +1
    • changedInput schema / properties / table / description
      Previous value: -"Database table to query"New value: +"TAP table, e.g. ps (Planetary Systems), pscomppars, cumulative (Kepler KOI), toi."
    • addedInput schema / properties / table / pattern
      Added value: +"^[A-Za-z_][A-Za-z0-9_]*$"
    • changedInput schema / properties / where / description
      Previous value: -"Filter conditions"New value: +"ADQL WHERE condition, e.g. disc_year > 2020 and discoverymethod = 'Transit'."
    • addedInput schema / properties / where / minLength
      Added value: +1
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare the full safety profile (readOnly, idempotent, non-destructive, open-world), so the description's marginal burden is low. It usefully adds that access goes through the TAP/ADQL service and that table names must be current, but says nothing about rate limits, result size behavior, or error handling.

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?

Two tight sentences, front-loaded with the core action and service, no filler. The second sentence is slightly redundant with the table parameter description but still earns its place by clarifying valid TAP names.

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 6-parameter, fully documented query tool with no output schema, the description is adequate but thin. It never states the return shape or that results are tabular rows from the selected columns, and gives no orientation on ADQL restrictions, leaving the agent to infer behavior from the schema alone.

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 coverage is 100%, so every parameter is already documented with examples (ADQL WHERE, ORDER BY, select list, format enum, limit bounds). The description repeats the table-name semantics rather than adding new meaning 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 (query) and resource (NASA Exoplanet Archive) via a named service (TAP/ADQL), and identifies the table namespace. It distinguishes the tool well from other NASA siblings by pointing at the Exoplanet Archive specifically, though it doesn't name any sibling it complements or overlaps with.

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?

Usage is only implied by the topic: there is no statement of when to reach for this tool versus e.g. jpl_sbdb, jpl_horizons, or the other NASA endpoints. No prerequisites, no exclusions, no alternatives named.

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