nasa-exoplanet-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_planetsA | Search for exoplanets in NASA's Exoplanet Archive with flexible filters. Returns matching planets from the Planetary Systems Composite Parameters table (one row per confirmed planet, best-available measurements). This is the primary tool for most exoplanet questions. All filter parameters are optional and can be combined. If no filters are given, returns the most recently discovered planets. For single-planet lookups by exact name, use get_planet instead. For complex queries needing GROUP BY, JOIN, spatial/cone searches, or querying tables other than the main planet catalog, use run_query instead. If a name-based search returns no results, the name may need resolving — try resolve_name first to find the canonical archive name. |
| get_planetA | Get comprehensive details for a single confirmed exoplanet by exact name. Returns all available properties organized into categories: orbital parameters, physical properties, stellar host properties, discovery information, system properties, and counts of available follow-up data. Use this after search_planets to get full details on a specific result, or when the user asks about a specific known planet. The planet name must be exact (e.g., 'Kepler-22 b', not 'Kepler-22b'). If unsure of the exact name, use resolve_name first to find the canonical archive name. Returns data from the Planetary Systems Composite Parameters table (best-available values across all published measurements). |
| resolve_nameA | Resolve any planet or star name, alias, or catalog identifier to its canonical name in the NASA Exoplanet Archive. Returns all known aliases grouped by catalog (Gaia, TIC, KOI, 2MASS, HD, HIP, etc.) and lists all confirmed planets in the system. Use this BEFORE get_planet or search_planets when the user provides a name that might not match the archive's naming convention. Common cases: missing spaces ('Kepler-22b' vs 'Kepler-22 b'), catalog IDs ('TIC 150428135'), alternate designations ('GJ 1214' vs 'Gliese 1214'), or informal names. Also useful when the user wants to know all designations for a star or system. |
| list_tablesA | List all available tables in the NASA Exoplanet Archive with descriptions. Returns table names, descriptions, approximate row counts, and guidance on what each table is used for. Use this to discover what data is available before writing queries with run_query. The most commonly used tables are: pscomppars (one row per confirmed planet, used by search_planets and get_planet), ps (all published measurements with multiple rows per planet), stellarhosts (host star properties), and toi (TESS candidate planets not yet confirmed). This tool returns a curated list of the most important tables. The archive has 40+ tables in total. To discover all of them, use run_query with: SELECT table_name, description FROM TAP_SCHEMA.tables ORDER BY table_name You do not need this tool for basic planet searches — search_planets already queries the right table. Use this when you need to query specialized tables like transit spectroscopy, microlensing, Kepler KOIs, or time series data via run_query. |
| list_columnsA | List available columns for a table in the NASA Exoplanet Archive, with data types, descriptions, and units. Use this to discover what data fields exist before selecting specific columns in search_planets or writing ADQL queries with run_query. The main planet table (pscomppars) has 300+ columns. Use the category filter to narrow results to a manageable set. You do not need this for basic queries — search_planets returns a useful default column set. Use this when the user asks about specific properties that may not be in the defaults, or before formulating a run_query call. |
| run_queryA | Execute a raw ADQL query against the NASA Exoplanet Archive TAP service. ADQL is an SQL-like language for astronomical databases. Use this for complex queries that search_planets cannot handle: GROUP BY aggregations, COUNT statistics, JOINs across tables, spatial/cone searches, queries against non-planet tables (toi, transitspec, emissionspec, ml, Kepler KOI tables), or any query needing full SQL-like flexibility. Use list_tables and list_columns first to discover available tables and column names. Common tables: pscomppars (one row per confirmed planet), ps (all published solutions — filter with default_flag=1 for one per planet), stellarhosts (host stars), toi (TESS candidates), transitspec (atmospheric transit spectra), emissionspec (atmospheric emission spectra), ml (microlensing planets). ADQL supports: SELECT, WHERE, ORDER BY, GROUP BY, COUNT, JOIN, LIKE, BETWEEN, IS NULL, IS NOT NULL, TOP, mathematical functions, and spatial functions (CONTAINS, POINT, CIRCLE for cone searches). Example cone search: WHERE CONTAINS(POINT('ICRS',ra,dec), CIRCLE('ICRS',291.0,48.0,5.0))=1 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/saikrmet/nasa-exoplanet-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server