Skip to main content
Glama

Nasa Power

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Climatology

climatology
Read-onlyIdempotent

Long-term monthly climatology averages for a coordinate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYes
communityNo
longitudeYes
parametersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
headerNoHeader information with temporal and geographic details
featuresNoArray of monthly climatology records
geometryNoGeographic geometry of the point
propertiesNoMetadata about the climatology request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 40.7128,
+    "longitude": -74.006
+  },
+  {
+    "community": "AG",
+    "latitude": -33.8688,
+    "longitude": 151.2093,
+    "parameters": "T2M,T2M_MAX,T2M_MIN,PRECTOTCORR"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Long-term monthly climatology averages from NASA POWER API",
+  "properties": {
+    "features": {
+      "description": "Array of monthly climatology records",
+      "items": {
+        "properties": {
+          "geometry": {
+            "description": "Geographic coordinates",
+            "type": "object"
+          },
+          "properties": {
+            "description": "Monthly average environmental parameters",
+            "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 climatology request",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering safety and idempotency. The description adds that it provides averages, which implies read-only aggregation, but does not disclose any additional behavioral traits (e.g., data source, limitations).

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?

The description is a single concise sentence. While it is efficiently front-loaded, it is so brief that it sacrifices essential detail, which is not ideal for completeness.

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

Completeness2/5

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

Despite having an output schema, the description lacks guidance on parameter usage and return values. For a tool with 4 parameters (2 required, 2 optional), the description is insufficient for the agent to reliably invoke it.

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

Parameters1/5

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

With 0% schema description coverage, the description must compensate, but it fails entirely. The parameters (latitude, longitude, community, parameters) are not explained, leaving the agent to infer their meaning and format from examples alone.

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?

The description clearly states it provides long-term monthly climatology averages for a coordinate, with a specific verb and resource. However, it could be more explicit about being historical averages versus current data, distinguishing it from siblings like point_data.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives like point_data or regional_data, leaving the agent without decision-making context.

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