Skip to main content
Glama
Sign In
ProgramComputer

NASA MCP Server

by ProgramComputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

NASA Mars Rover Photos (retired upstream)

nasa_mars_rover
Read-onlyIdempotent

Fetch Mars rover photos by rover, sol, or Earth date and camera; returns image links or accurate upstream status, without fabricating results.

Instructions

DEPRECATED: the upstream Mars Rover Photos API (api.nasa.gov/mars-photos) has been returning HTTP 404 "No such app" since at least 2026-09-29. Calls still query it and report the upstream status accurately; no photos are fabricated. Requires NASA_API_KEY.

Input Schema

NameRequiredDescriptionDefault
solNoMartian sol of the photos. Provide sol or earth_date.
pageNoResult page (25 photos per page).
roverYesRover name.
cameraNoCamera abbreviation, e.g. FHAZ, NAVCAM.
earth_dateNoEarth date of the photos (YYYY-MM-DD). Provide sol or earth_date.
max_imagesNoHow many photos to embed (0-5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / camera / description
      Previous value: -"Camera name"New value: +"Camera abbreviation, e.g. FHAZ, NAVCAM."
    • addedInput schema / properties / camera / pattern
      Added value: +"^[A-Za-z_]+$"
    • changedInput schema / properties / earth_date / description
      Previous value: -"Earth date of the photos (YYYY-MM-DD)"New value: +"Earth date of the photos (YYYY-MM-DD). Provide sol or earth_date."
    • addedInput schema / properties / max_images
      Added value: +{
+  "default": 3,
+  "description": "How many photos to embed (0-5).",
+  "maximum": 5,
+  "minimum": 0,
+  "type": "integer"
+}
    • changedInput schema / properties / page / description
      Previous value: -"Page number for pagination"New value: +"Result page (25 photos per page)."
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / rover / description
      Previous value: -"Name of the rover (curiosity, opportunity, spirit, perseverance)"New value: +"Rover name."
    • addedInput schema / properties / rover / enum
      Added value: +[
+  "curiosity",
+  "opportunity",
+  "perseverance",
+  "spirit"
+]
    • changedInput schema / properties / sol / description
      Previous value: -"Martian sol (day) of the photos"New value: +"Martian sol of the photos. Provide sol or earth_date."
    • addedInput schema / properties / sol / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / sol / minimum
      Added value: +0
    • changedInput schema / properties / sol / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds context the annotations cannot: that the upstream is dead, that calls still accurately report the upstream status, that no photos are fabricated, and that a NASA_API_KEY is required. This is exactly the extra behavioral disclosure expected.

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 deprecation warning is front-loaded in the first clause, followed by the precise failure mode and the key operational facts. Three compact sentences with no waste.

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?

For a read-only, open-world API tool with a fully documented input schema and no output schema, the description supplies everything an agent needs before calling: deprecation status, upstream behavior, honesty guarantee, and the API key requirement.

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 the schema already documents all six parameters including the sol/earth_date alternative and the max_images range. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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 the resource (Mars Rover Photos API) and its exact current state (upstream 404 'No such app' since 2026-09-29). It clearly communicates what the tool does (still queries the upstream and reports status) but does not explicitly differentiate itself from any sibling tool, so it stops short of 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?

The DEPRECATED label and the 404 detail give strong implicit guidance that this tool should not be selected for photo retrieval. It does not, however, name an alternative tool or state an explicit 'use X instead' condition, which would be needed for 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