Skip to main content
Glama
ProgramComputer

NASA MCP Server

by ProgramComputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

NASA EPIC Earth imagery

nasa_epic
Read-onlyIdempotent

Fetch DSCOVR EPIC full-disc Earth images for a day, listing metadata for all and embedding up to three JPEGs, with natural or enhanced collection options.

Instructions

Earth Polychromatic Imaging Camera (DSCOVR) full-disc Earth images for a day: metadata for every image plus a bounded number embedded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate of the images (YYYY-MM-DD). Defaults to the most recent available day.
collectionNoImage collection.natural
max_imagesNoHow many images to embed (0-3, JPEG). All images are listed with PNG and JPEG URLs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / collection / default
      Added value: +"natural"
    • changedInput schema / properties / collection / description
      Previous value: -"Image collection (natural or enhanced)"New value: +"Image collection."
    • addedInput schema / properties / collection / enum
      Added value: +[
+  "natural",
+  "enhanced"
+]
    • changedInput schema / properties / date / description
      Previous value: -"Date of the image (YYYY-MM-DD)"New value: +"Date of the images (YYYY-MM-DD). Defaults to the most recent available day."
    • addedInput schema / properties / max_images
      Added value: +{
+  "default": 1,
+  "description": "How many images to embed (0-3, JPEG). All images are listed with PNG and JPEG URLs.",
+  "maximum": 3,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: every image's metadata is returned while only a bounded number are embedded as JPEGs, which shapes expectations about response size. It says nothing about rate limits or the upstream DSCOVR availability window.

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 front-loaded sentence with a colon-delimited clause that puts the resource first and the return shape second. No filler, though the parenthetical instrument expansion makes it slightly dense to parse.

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?

All three parameters are optional and fully documented in the schema, and the description covers what comes back (full metadata, bounded embeds). With no output schema, it adequately sets expectations for a read-only imagery lookup; only upstream availability caveats are absent.

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 date, collection and max_images are fully documented in the schema, including defaults and the 0-3 bound. The description only vaguely gestures at 'a bounded number embedded' and 'for a day', which the schema states more precisely, so it adds little beyond the structured fields.

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?

Names the specific instrument (Earth Polychromatic Imaging Camera on DSCOVR) and the resource (full-disc Earth images for a day), and states what the response contains: metadata for every image plus a bounded number embedded. It does not explicitly distinguish itself from siblings like nasa_images, nasa_apod or nasa_gibs, but the instrument naming makes the scope identifiable.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative-tool guidance. 'For a day' implies the retrieval context, but an agent choosing between nasa_epic, nasa_images and nasa_apod gets no routing help from the description.

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