Skip to main content
Glama
Sign In
ProgramComputer

NASA MCP Server

by ProgramComputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

NASA Image and Video Library search

nasa_images
Read-onlyIdempotent

Search NASA's Image and Video Library by free text, media type, and year range. Get item metadata, URLs, and up to five preview thumbnails for research or content workflows.

Instructions

Search NASA's Image and Video Library. Returns item metadata and URLs, with a bounded number of preview thumbnails embedded.

Input Schema

NameRequiredDescriptionDefault
qYesFree-text search terms.
pageNoResult page (1-based).
year_endNoLatest year (YYYY).
page_sizeNoResults per page (1-100).
max_imagesNoHow many preview thumbnails to embed (0-5). Every item is listed with its URLs.
media_typeNoRestrict to one media type.
year_startNoEarliest year (YYYY).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / max_images
      Added value: +{
+  "default": 3,
+  "description": "How many preview thumbnails to embed (0-5). Every item is listed with its URLs.",
+  "maximum": 5,
+  "minimum": 0,
+  "type": "integer"
+}
    • changedInput schema / properties / media_type / description
      Previous value: -"Media type (image, video, audio)"New value: +"Restrict to one media type."
    • addedInput schema / properties / media_type / enum
      Added value: +[
+  "image",
+  "video",
+  "audio"
+]
    • addedInput schema / properties / page / default
      Added value: +1
    • changedInput schema / properties / page / description
      Previous value: -"Page number for pagination"New value: +"Result page (1-based)."
    • addedInput schema / properties / page / maximum
      Added value: +100
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page_size
      Added value: +{
+  "default": 10,
+  "description": "Results per page (1-100).",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / q / description
      Previous value: -"Search query"New value: +"Free-text search terms."
    • addedInput schema / properties / q / minLength
      Added value: +1
    • changedInput schema / properties / year_end / description
      Previous value: -"End year for results"New value: +"Latest year (YYYY)."
    • addedInput schema / properties / year_end / pattern
      Added value: +"^\\d{4}$"
    • changedInput schema / properties / year_start / description
      Previous value: -"Start year for results"New value: +"Earliest year (YYYY)."
    • addedInput schema / properties / year_start / pattern
      Added value: +"^\\d{4}$"
  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=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety and idempotency profile is covered. The description adds the useful behavioral fact that results are bounded thumbnails plus metadata URLs, but says nothing about rate limits, auth, or pagination beyond what the schema implies.

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?

Two compact sentences, front-loaded with the action and resource, followed by the return behavior. No filler or redundancy; slightly more detail on distinctions from siblings would still earn its place.

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?

With no output schema and seven parameters, the description does the necessary work of sketching the return shape (metadata, URLs, embedded preview thumbnails), which is the main gap structured data leaves. Routing guidance relative to sibling NASA media tools is the only missing piece.

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 every parameter (q, page, page_size, max_images, media_type, year_start, year_end) is already documented in the schema. The description's only added semantic is that thumbnails are 'bounded', which mirrors the max_images schema entry. Baseline 3 is correct when the schema carries this much weight.

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?

States a specific verb (Search) and resource (NASA's Image and Video Library) and specifies the return shape (item metadata and URLs, embedded thumbnails). It does not explicitly differentiate itself from media-adjacent siblings like nasa_apod, nasa_eonet, or nasa_gibs, but the resource name is unambiguous.

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?

No guidance on when to use this tool versus alternatives such as nasa_apod or nasa_eonet, no prerequisites, and no exclusions. An agent must infer usage from the name alone.

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