MCP TypeScript NASA Server

nasa_neo_feed

Retrieve data on asteroids passing near Earth within a specified date range to monitor potential impact risks and track celestial objects.

Instructions

Get Near Earth Objects (asteroids) passing near Earth within a date range

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nasa_neo_feed"
  }
}

Input Schema

Name	Required	Description	Default
`start_date`	No	Start date in YYYY-MM-DD format. Defaults to today.
`end_date`	No	End date in YYYY-MM-DD format. Defaults to 7 days from start date.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 11, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but lacks critical behavioral details: it doesn't mention rate limits, authentication requirements, data freshness, error conditions, or what the return format looks like (especially important since there's 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.

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple data retrieval tool and front-loads the essential information.

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

Completeness2/5

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

Given the absence of annotations and output schema, the description is incomplete. It doesn't explain what data is returned (e.g., asteroid names, sizes, distances), how results are structured, or any behavioral constraints. For a tool with no structured metadata, the description should provide more context about the operation.

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?

The schema description coverage is 100%, with both parameters clearly documented in the input schema. The description adds no additional parameter semantics beyond what's already in the schema (e.g., it doesn't explain date range constraints beyond 'within a date range'). Baseline 3 is appropriate when the schema does the heavy lifting.

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 the verb 'Get' and the resource 'Near Earth Objects (asteroids) passing near Earth within a date range'. It specifies the exact scope (asteroids passing near Earth) and distinguishes it from sibling tools like NASA APOD or Mars rover photos, which serve completely different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage for retrieving asteroid data within a date range, but provides no explicit guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, exclusions, or compare it to other asteroid-related tools (though none are listed among siblings).

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

Deploy Server