Skip to main content
Glama
Sign In
ProgramComputer

NASA MCP Server

by ProgramComputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

NASA Near Earth Object Web Service

nasa_neo
Read-onlyIdempotent

Fetch near-Earth asteroid close approaches for up to 7 days or query a single asteroid by ID from NASA NeoWs.

Instructions

Near-Earth asteroid close approaches from NASA NeoWs: a feed for up to 7 days (defaults to today, UTC) or a single asteroid by ID. Requires NASA_API_KEY.

Input Schema

NameRequiredDescriptionDefault
end_dateNoEnd date (YYYY-MM-DD), at most 7 days after start_date. Defaults to start_date.
start_dateNoStart date for the close-approach feed (YYYY-MM-DD). Defaults to today (UTC).
asteroid_idNoLook up one asteroid by its NeoWs ID instead of the date feed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / asteroid_id / description
      Previous value: -"ID of a specific asteroid"New value: +"Look up one asteroid by its NeoWs ID instead of the date feed."
    • addedInput schema / properties / asteroid_id / pattern
      Added value: +"^\\d+$"
    • changedInput schema / properties / end_date / description
      Previous value: -"End date for asteroid search (YYYY-MM-DD)"New value: +"End date (YYYY-MM-DD), at most 7 days after start_date. Defaults to start_date."
    • changedInput schema / properties / start_date / description
      Previous value: -"Start date for asteroid search (YYYY-MM-DD)"New value: +"Start date for the close-approach feed (YYYY-MM-DD). Defaults to today (UTC)."
    • removedInput schema / required
      Removed value: -[
-  "start_date",
-  "end_date"
-]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds two things annotations do not: the auth requirement (NASA_API_KEY) and the hard 7-day window constraint, both of which affect whether a call can succeed.

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 dense sentence that front-loads the resource and enumerates the two modes without filler. It is slightly overloaded with parentheticals, but every clause carries information.

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

Completeness4/5

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

With no output schema, the description carries some burden for return expectations, and it names what the feed contains (close approaches) and its date scope. Combined with full schema coverage and read-only annotations, an agent has what it needs, though a word on response shape would be ideal.

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%, so every parameter's format, default and constraint is already documented. The description restates the 7-day limit, today-UTC default and ID-lookup mode rather than adding new syntax or edge-case meaning, so it sits at the baseline for a fully documented 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?

The description names a specific resource and two distinct modes: a close-approach date feed (up to 7 days, default today UTC) and a single-asteroid lookup by ID. That is enough for an agent to know exactly what the tool returns. It does not differentiate itself from orbit/catalog siblings like jpl_cad or jpl_sbdb, which keeps it from 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly explains that asteroid_id selects a single-object lookup 'instead of the date feed', giving an agent the condition for choosing each mode, and states the NASA_API_KEY prerequisite. There are no explicit 'when-not-to-use' rules or named alternative tools, so it stops short of a 5.

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