Skip to main content
Glama
Sign In
ProgramComputer

NASA MCP Server

by ProgramComputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

NASA Astronomy Picture of the Day

nasa_apod
Read-onlyIdempotent

Fetch NASA's Astronomy Picture of the Day for one date or up to 100-day range, returning title, explanation, media URL, page link, and embedded images. No API key needed.

Instructions

NASA's Astronomy Picture of the Day (APOD) from the NASA Science APOD API (science.nasa.gov): the latest picture, one date (1995-06-16 onward), or a date range of up to 100 days. Returns the title, credit, explanation as plain text, image or video URL and page link, and embeds up to max_images pictures. No API key needed.

Input Schema

NameRequiredDescriptionDefault
dateNoDate of the picture (YYYY-MM-DD, 1995-06-16 or later). Defaults to the latest published picture. Cannot be combined with start_date/end_date.
end_dateNoEnd of a date range (YYYY-MM-DD); requires start_date. Defaults to today (UTC) when start_date is given.
max_imagesNoHow many pictures to embed as image content (0-5). Remaining entries are listed by URL.
start_dateNoStart of a date range (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / count
      Removed value: -{
-  "description": "Count of random APODs to retrieve",
-  "type": "number"
-}
    • changedInput schema / properties / date / description
      Previous value: -"The date of the APOD image to retrieve (YYYY-MM-DD)"New value: +"Date of the picture (YYYY-MM-DD, 1995-06-16 or later). Defaults to the latest published picture. Cannot be combined with start_date/end_date."
    • changedInput schema / properties / end_date / description
      Previous value: -"End date for date range search (YYYY-MM-DD)"New value: +"End of a date range (YYYY-MM-DD); requires start_date. Defaults to today (UTC) when start_date is given."
    • addedInput schema / properties / max_images
      Added value: +{
+  "default": 1,
+  "description": "How many pictures to embed as image content (0-5). Remaining entries are listed by URL.",
+  "maximum": 5,
+  "minimum": 0,
+  "type": "integer"
+}
    • changedInput schema / properties / start_date / description
      Previous value: -"Start date for date range search (YYYY-MM-DD)"New value: +"Start of a date range (YYYY-MM-DD)."
    • removedInput schema / properties / thumbs
      Removed value: -{
-  "description": "Return URL of thumbnail for video content",
-  "type": "boolean"
-}
    • removedInput schema / required
      Removed value: -[
-  "date"
-]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive; the description adds genuinely new behavioral facts: no API key is required, the date range is capped at 100 days, and images are embedded up to max_images with the rest listed by URL. It doesn't mention rate limits or error handling, so it's not a 5.

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, front-loaded with the source and access modes, then the return shape and the no-key note. No filler, though the packing of modes, bounds, and outputs into one sentence makes it slightly heavy.

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?

With no output schema, the description steps in to describe return fields (title, credit, plain-text explanation, image/video URL, page link) and the embedding behavior. Combined with mode constraints and the no-key note, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds a constraint not present in the schema: the date range cannot exceed 100 days. It also summarizes the date/range interaction, giving real value beyond the schema text.

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?

States a specific verb+resource (retrieves NASA's Astronomy Picture of the Day from the NASA Science APOD API) and enumerates the three access modes: latest, single date, or range. This clearly separates it from siblings like nasa_images and nasa_epic.

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?

Explains the three usage modes and the 100-day range limit, plus the 1995-06-16 lower bound. It does not explicitly say when to prefer this over nasa_images or nasa_epic, so it stops short of full alternative routing.

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