Skip to main content
Glama
Sign In
ProgramComputer

NASA MCP Server

by ProgramComputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

NASA GIBS satellite imagery

nasa_gibs
Read-onlyIdempotent

Render NASA GIBS satellite imagery for a specific date and bounding box as an image. Provide a layer, date, and optional area to get a WMS map.

Instructions

Render a Global Imagery Browse Services (GIBS) layer for a date and bounding box as an image (WMS GetMap, EPSG:4326).

Input Schema

NameRequiredDescriptionDefault
bboxNoArea as west,south,east,north in decimal degrees (EPSG:4326). Defaults to the whole globe.
dateYesImagery date (YYYY-MM-DD).
layerYesGIBS layer identifier, e.g. MODIS_Terra_CorrectedReflectance_TrueColor
formatNoImage format.png
resolutionNoOutput resolution in pixels per degree (default 2, i.e. 720x360 for the whole globe).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / bbox
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "items": {
+        "type": "number"
+      },
+      "maxItems": 4,
+      "minItems": 4,
+      "type": "array"
+    }
+  ],
+  "description": "Area as west,south,east,north in decimal degrees (EPSG:4326). Defaults to the whole globe."
+}
    • changedInput schema / properties / date / description
      Previous value: -"Date of imagery (YYYY-MM-DD)"New value: +"Imagery date (YYYY-MM-DD)."
    • addedInput schema / properties / format / default
      Added value: +"png"
    • changedInput schema / properties / format / description
      Previous value: -"Image format (png, jpg, jpeg)"New value: +"Image format."
    • addedInput schema / properties / format / enum
      Added value: +[
+  "png",
+  "jpg",
+  "jpeg"
+]
    • changedInput schema / properties / layer / description
      Previous value: -"Layer name (e.g., MODIS_Terra_CorrectedReflectance_TrueColor)"New value: +"GIBS layer identifier, e.g. MODIS_Terra_CorrectedReflectance_TrueColor"
    • addedInput schema / properties / layer / pattern
      Added value: +"^[A-Za-z0-9_.-]+$"
    • addedInput schema / properties / resolution / default
      Added value: +2
    • changedInput schema / properties / resolution / description
      Previous value: -"Resolution in pixels per degree"New value: +"Output resolution in pixels per degree (default 2, i.e. 720x360 for the whole globe)."
    • addedInput schema / properties / resolution / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / resolution / maximum
      Added value: +40
  2. First observed

TDQS

B3.4/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 protocol context (WMS GetMap, EPSG:4326) and that the output is an image, but says nothing about rate limits, tile capping, or what happens with unsupported layer/date combinations.

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?

A single tight sentence front-loads the verb and resource, then packs protocol and projection into a parenthetical. Nothing is wasted and nothing is buried.

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, the description correctly states the return type (an image) and the projection, and annotations cover the safety profile. Minor gaps remain around image size limits and whether the layer identifier must be a known GIBS layer, but an agent can call this successfully as written.

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 all five parameters are already documented in the schema (bbox format, date format, layer pattern, format enum, resolution default). The description only restates that date and bbox are the inputs, adding no syntax or constraint detail beyond what the schema provides. 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?

States a specific verb (Render), resource (GIBS layer), and the underlying mechanism (WMS GetMap, EPSG:4326), so an agent knows exactly what operation this performs. It does not differentiate itself from siblings such as nasa_trek_tile or nasa_images, which an agent choosing between imagery tools would benefit from.

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?

The description gives no when-to-use guidance, no prerequisites, and does not name any alternative among the many NASA/JPL imagery siblings. The agent must infer usage entirely from the layer/date requirement.

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