Skip to main content
Glama

Nasa Power

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Regional Data

regional_data
Read-onlyIdempotent

Bounding-box query — daily or monthly data over a rectangular region. Bbox area max ~10° × 10°.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesYYYYMMDD
startYesYYYYMMDD
temporalNodaily (default) | monthly
communityNo
parametersNo
latitude_maxYes
latitude_minYes
longitude_maxYes
longitude_minYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
headerNoHeader information with temporal and geographic bounds
featuresNoArray of regional data records
geometryNoGeographic geometry of the region
propertiesNoMetadata about the regional request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "end": "20231231",
+    "latitude_max": 41,
+    "latitude_min": 39,
+    "longitude_max": -73,
+    "longitude_min": -75,
+    "start": "20230101"
+  },
+  {
+    "community": "RE",
+    "end": "20231231",
+    "latitude_max": 36,
+    "latitude_min": 34,
+    "longitude_max": 140,
+    "longitude_min": 138,
+    "parameters": "T2M,ALLSKY_SFC_SW_DWN,WS10M",
+    "start": "20230101",
+    "temporal": "monthly"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Regional bounding-box data from NASA POWER API",
+  "properties": {
+    "features": {
+      "description": "Array of regional data records",
+      "items": {
+        "properties": {
+          "geometry": {
+            "description": "Geographic coordinates within region",
+            "type": "object"
+          },
+          "properties": {
+            "description": "Environmental parameters for region cell",
+            "type": "object"
+          },
+          "type": {
+            "description": "GeoJSON feature type",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "geometry": {
+      "description": "Geographic geometry of the region",
+      "type": "object"
+    },
+    "header": {
+      "description": "Header information with temporal and geographic bounds",
+      "type": "object"
+    },
+    "properties": {
+      "description": "Metadata about the regional request",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint false. The description adds useful behavioral constraints like max bbox area (10°×10°) and temporal granularity options, which go beyond annotations.

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?

Single sentence that is front-loaded with the core concept ('Bounding-box query') and concisely conveys key options and constraints. No wasted words.

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

Completeness3/5

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

With output schema present, return values need not be described. However, the description omits the data domain (meteorological) and does not clarify the meaning of community or parameters fields. It is adequate but leaves some usage context unclear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema coverage is only 33%, with most parameters lacking descriptions. The description does not add meaning to undocumented parameters like community and parameters. It only implies temporal parameter options but does not explain their constraints or format, leaving gaps.

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?

The description clearly states 'Bounding-box query' and specifies temporal options and spatial constraint. It distinguishes from sibling tools like point_data and climatology by explicitly describing a rectangular region query.

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

Usage Guidelines3/5

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

The description implies usage for rectangular region queries but does not explicitly state when to use vs alternatives (e.g., point_data for points) or provide when-not scenarios. The max area constraint is mentioned but no further guidance.

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

All Nasa Power toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources