Nasa

Get Asteroids

get_asteroids

Read-onlyIdempotent

Get near-Earth asteroids approaching within a date range (max 7 days). Returns size, velocity, and miss distance. Example: get_asteroids({ start_date: "2024-01-01", end_date: "2024-01-07", _apiKey: "DEMO_KEY" })

Input Schema

TableJSON Schema

Name	Required	Description
`_apiKey`	No	NASA API key (optional, defaults to DEMO_KEY)
`end_date`	Yes	End date in YYYY-MM-DD format (max 7 days after start)
`start_date`	Yes	Start date in YYYY-MM-DD format

Output Schema

TableJSON Schema

Name	Required	Description	Default
`asteroids`	Yes	List of near-Earth asteroids (up to 30)
`total_count`	Yes	Total count of near-Earth objects in the date range

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "_apiKey": "your-nasa-api-key",
-    "end_date": "2024-01-07",
-    "start_date": "2024-01-01"
-  },
-  {
-    "_apiKey": "your-nasa-api-key",
-    "end_date": "2024-02-15",
-    "start_date": "2024-02-10"
-  }
-]New value: +[
+  {
+    "end_date": "2024-01-07",
+    "start_date": "2024-01-01"
+  },
+  {
+    "end_date": "2024-02-15",
+    "start_date": "2024-02-10"
+  }
+]

First observedJun 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds useful operational details beyond the annotations: the 7-day limit, the nature of returned data (size, velocity, miss distance), and a concrete invocation example. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded, with the core purpose stated in the first sentence. The example is useful and does not bloat the text.

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

Completeness5/5

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

Given the schema fully documents the two required date parameters and the optional API key, and an output schema exists for return values, the description covers the remaining essential context: the 7-day window and what the returned data will include.

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?

Input schema coverage is 100%, so the parameters are already well documented. The description's example reinforces usage but mostly repeats information already present in the schema, adding only marginal extra meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool retrieves near-Earth asteroids within a date range, and specifies the kind of data returned (size, velocity, miss distance). This resource-focused description distinguishes it from the other NASA and astronomy-oriented sibling tools without ambiguity.

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?

The description conveys when to use the tool: when near-Earth asteroid approach data is needed for a date range. It also provides an important usage constraint (max 7 days), though it does not explicitly call out alternative tools or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nasa tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.