Skip to main content
Glama

Get Mars Photos

get_mars_photos
Read-onlyIdempotent

"Show me photos from the Mars rover" / "Perseverance images from sol 1000" / "latest pictures from Mars", raw images from NASA's Perseverance rover (Mars 2020), straight off the mars.nasa.gov feed. Filter by Martian sol and by camera. Returns image URLs at four resolutions, the sol, the UTC and Mars-local capture times, and the camera instrument. Keyless. Covers Perseverance only, Curiosity, Opportunity and Spirit have no live public image feed. Example: get_mars_photos({ sol: 1000, camera: "NAVCAM_LEFT" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sol": 1000,
      "camera": "NAVCAM_LEFT"
    },
    "name": "get_mars_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
solNoMartian sol (mission day) to retrieve images from, e.g. 1000. Perseverance landed on sol 0 (2021-02-18) and is past sol 1900. Omit for the most recent images.
limitNoMax images to return (default 20, max 100).
cameraNoCamera instrument, exact: "NAVCAM_LEFT", "NAVCAM_RIGHT", "FRONT_HAZCAM_LEFT_A", "FRONT_HAZCAM_RIGHT_A", "REAR_HAZCAM_LEFT", "REAR_HAZCAM_RIGHT", "MCZ_LEFT"/"MCZ_RIGHT" (Mastcam-Z), "SHERLOC_WATSON", "SUPERCAM_RMI", "SKYCAM", "PIXL_MCC", "CACHECAM". Short forms FHAZ/RHAZ/NAVCAM/MAST are accepted. Optional.

Output Schema

NameRequiredDescriptionDefault
solNo
countNoTotal number of photos retrieved
roverNo
cameraNo
photosNoList of Mars rover photos (up to 20)
total_matchingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / camera / type
      Previous value: -"null"New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / sol / type
      Previous value: -"null"New value: +[
      +  "null",
      +  "number"
      +]
  2. Changed22 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "_apiKey": "your-nasa-api-key",
      -    "camera": "FHAZ",
      -    "sol": 1000
      -  },
      -  {
      -    "_apiKey": "your-nasa-api-key",
      -    "sol": 3000
      -  }
      -]New value: +[
      +  {
      +    "camera": "NAVCAM_LEFT",
      +    "sol": 1000
      +  },
      +  {
      +    "limit": 10,
      +    "sol": 1500
      +  }
      +]
    • removedInput schema / properties / _apiKey
      Removed value: -{
      -  "description": "NASA API key (optional, defaults to DEMO_KEY)",
      -  "type": "string"
      -}
    • changedInput schema / properties / camera / description
      Previous value: -"Camera abbreviation: \"FHAZ\" (front hazard), \"RHAZ\" (rear hazard), \"MAST\" (mast), \"CHEMCAM\", \"MAHLI\", \"MARDI\", \"NAVCAM\" (optional)"New value: +"Camera instrument, exact: \"NAVCAM_LEFT\", \"NAVCAM_RIGHT\", \"FRONT_HAZCAM_LEFT_A\", \"FRONT_HAZCAM_RIGHT_A\", \"REAR_HAZCAM_LEFT\", \"REAR_HAZCAM_RIGHT\", \"MCZ_LEFT\"/\"MCZ_RIGHT\" (Mastcam-Z), \"SHERLOC_WATSON\", \"SUPERCAM_RMI\", \"SKYCAM\", \"PIXL_MCC\", \"CACHECAM\". Short forms FHAZ/RHAZ/NAVCAM/MAST are accepted. Optional."
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Max images to return (default 20, max 100).",
      +  "type": "number"
      +}
    • changedInput schema / properties / sol / description
      Previous value: -"Martian sol (day) to retrieve photos from, e.g. 1000 (default: 1000)"New value: +"Martian sol (mission day) to retrieve images from, e.g. 1000. Perseverance landed on sol 0 (2021-02-18) and is past sol 1900. Omit for the most recent images."
    • addedOutput schema / properties / camera
      Added value: +{
      +  "type": "null"
      +}
    • removedOutput schema / properties / photos / items / properties / camera_full_name
      Removed value: -{
      -  "description": "Full name of the camera",
      -  "type": "string"
      -}
    • addedOutput schema / properties / photos / items / properties / credit
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / photos / items / properties / filter
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / photos / items / properties / full_res_url
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / photos / items / properties / id / type
      Previous value: -"number"New value: +"string"
    • addedOutput schema / properties / photos / items / properties / mars_time
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / photos / items / properties / page_url
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / photos / items / properties / rover
      Removed value: -{
      -  "description": "Name of the rover (Curiosity, Opportunity, Spirit)",
      -  "type": "string"
      -}
    • removedOutput schema / properties / photos / items / properties / rover_status
      Removed value: -{
      -  "description": "Current status of the rover",
      -  "type": "string"
      -}
    • addedOutput schema / properties / photos / items / properties / thumbnail_url
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / photos / items / properties / title
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / photos / items / required
      Removed value: -[
      -  "id",
      -  "sol",
      -  "camera",
      -  "camera_full_name",
      -  "image_url",
      -  "earth_date",
      -  "rover",
      -  "rover_status"
      -]
    • addedOutput schema / properties / rover
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / sol
      Added value: +{
      +  "type": "null"
      +}
    • addedOutput schema / properties / total_matching
      Added value: +{
      +  "type": "number"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "count",
      -  "photos"
      -]
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful context beyond that: keyless access and the mars.nasa.gov source feed. It does not discuss rate limits, pagination, or failure modes when a sol has no images, which keeps it at a solid 3.

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?

Front-loads natural-language query examples before the technical detail, which aids matching. It is slightly dense in the middle but every sentence carries information; nothing is redundant filler.

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

Completeness4/5

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

An output schema exists, so return values need not be spelled out, yet the description still names the returned fields (four resolutions, sol, UTC and Mars-local times, camera). Combined with rich annotations and full schema coverage, 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.

Parameters3/5

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

Schema description coverage is 100%, with sol, limit and camera all documented including camera short forms, so the schema does the heavy lifting. The description only restates that filtering is by sol and camera and repeats an example already present in the schema's examples array, adding little new 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?

States a specific verb and resource (raw images from NASA's Perseverance rover) and immediately bounds scope: 'Covers Perseverance only, Curiosity, Opportunity and Spirit have no live public image feed.' An agent knows exactly what this retrieves and what it does not.

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?

Gives concrete trigger phrasings, an example call, and the key usage rule 'Omit for the most recent images.' It also states the negative scope (no live feed for other rovers). No sibling tool covers Mars imagery, so the absence of an explicit alternative is not a real gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.