MCP server for NASA API integration, providing access to Near Earth Object data
Single tool 'getNeo' has a clear verb-noun name and reasonable description (127 chars, within 10-1024 range). However, critical gaps undermine quality: parameter descriptions are minimal and lack format/constraint details; output schema is completely undocumented (tool returns response.text, a raw string with no structure); no error handling guidance; no pagination despite potentially large result sets; API key exposed in code (security risk). The tool is functional but falls short of production standards.
Get NEO (Nasa's Near Earth Object) by date, if an end date is not provided use start date as end date. Please use YYYY-MM-DD date time format.
Output schema completely undocumented. Tool returns response.text (raw string) with no structure, field names, or type information. LLMs cannot parse or chain results.
API key hardcoded in source and exposed via environment variable. Should use server-side secret injection; credentials in code risk leakage in version control and logs.
Parameter descriptions lack actionable detail. 'Start date of the request use YYYY-MM-DD format please' is vague; should specify: required, format pattern, valid range (e.g. past 60 days), and what happens if end_date is omitted.
No error handling or recovery guidance. If NASA API returns 400 (invalid date), 401 (bad key), or 429 (rate limit), the raw response.text is returned with no actionable message for the LLM.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
No pagination or result limits. NASA NEO API can return hundreds of objects; returning all as raw text will exhaust context windows and degrade LLM reasoning.