Skip to main content
Glama

Nasa Power

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Point Data

point_data
Read-onlyIdempotent

Time-series observations for a single coordinate. Temporal granularity controlled by the dates supplied — both must be YYYYMMDD; use daily by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesEnd date YYYYMMDD
startYesStart date YYYYMMDD
latitudeYesLatitude in degrees (-90 to 90)
temporalNohourly | daily (default) | monthly
communityNoAG (agriculture, default) | RE (renewable energy) | SB (sustainable buildings)
longitudeYesLongitude in degrees (-180 to 180)
parametersNoComma-separated POWER parameter codes (default T2M,T2M_MAX,T2M_MIN,PRECTOTCORR,ALLSKY_SFC_SW_DWN,RH2M,WS10M)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
headerNoHeader information with temporal and geographic details
featuresNoArray of time-series data records
geometryNoGeographic geometry of the point
propertiesNoMetadata about the request and data

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "end": "20231231",
+    "latitude": 40.7128,
+    "longitude": -74.006,
+    "start": "20230101"
+  },
+  {
+    "community": "RE",
+    "end": "20230630",
+    "latitude": 35.6762,
+    "longitude": 139.6503,
+    "parameters": "T2M,PRECTOTCORR,ALLSKY_SFC_SW_DWN",
+    "start": "20230601",
+    "temporal": "hourly"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Time-series observations for a single coordinate from NASA POWER API",
+  "properties": {
+    "features": {
+      "description": "Array of time-series data records",
+      "items": {
+        "properties": {
+          "geometry": {
+            "description": "Geographic coordinates",
+            "type": "object"
+          },
+          "properties": {
+            "description": "Environmental parameters and observations",
+            "type": "object"
+          },
+          "type": {
+            "description": "GeoJSON feature type",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "geometry": {
+      "description": "Geographic geometry of the point",
+      "type": "object"
+    },
+    "header": {
+      "description": "Header information with temporal and geographic details",
+      "type": "object"
+    },
+    "properties": {
+      "description": "Metadata about the request and data",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so safety is well-covered. The description adds date format constraints and default temporal granularity beyond what annotations provide.

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?

Two concise sentences: the first states the purpose, the second adds key constraints. No redundant information.

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

Completeness5/5

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

With a full input schema (100% covered) and an output schema present, the description provides sufficient context for a complete understanding, including date format and default granularity.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds meaning by specifying that dates must be YYYYMMDD and that temporal defaults to daily, which are not fully captured in schema descriptions.

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 the tool returns 'time-series observations for a single coordinate', which is specific and distinct from sibling tools like 'regional_data' or 'climatology' that aggregate over areas or multiple points.

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 single-point time-series queries with date control, but it does not explicitly state when to use this tool over alternatives, nor does it provide exclusions or prerequisites.

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