NASA MCP Server

NASA POWER daily point data

nasa_power

Read-onlyIdempotent

Fetch daily solar and meteorological values for a latitude/longitude over a date range, selecting parameters for renewable energy, buildings, or agriculture.

Instructions

Daily solar and meteorological data for a point from NASA POWER (Prediction Of Worldwide Energy Resources).

Input Schema

Name	Required	Description	Default
`end`	Yes	End date (YYYYMMDD).
`start`	Yes	Start date (YYYYMMDD).
`format`	No	Response format.	json
`latitude`	Yes	Latitude in decimal degrees.
`community`	Yes	User community: RE (renewable energy), SB (sustainable buildings), AG (agroclimatology).
`longitude`	Yes	Longitude in decimal degrees.
`parameters`	Yes	Comma-separated POWER parameters, e.g. T2M,PRECTOTCORR,WS10M.
`time_standard`	No	Time standard for daily values; POWER defaults to LST (local solar time) when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv1.2.0Oct 1, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / community / description

Previous value: -"User community (RE, SB, AG, etc.)"New value: +"User community: RE (renewable energy), SB (sustainable buildings), AG (agroclimatology)."

addedInput schema / properties / community / enum
```
Added value: +[
+  "RE",
+  "SB",
+  "AG"
+]
```

changedInput schema / properties / end / description

Previous value: -"End date (YYYYMMDD)"New value: +"End date (YYYYMMDD)."

addedInput schema / properties / format / default
```
Added value: +"json"
```

changedInput schema / properties / format / description

Previous value: -"Response format (json, csv, etc.)"New value: +"Response format."

addedInput schema / properties / format / enum
```
Added value: +[
+  "json",
+  "csv"
+]
```

changedInput schema / properties / latitude / description

Previous value: -"Latitude coordinate"New value: +"Latitude in decimal degrees."

addedInput schema / properties / latitude / maximum
```
Added value: +90
```
addedInput schema / properties / latitude / minimum
```
Added value: +-90
```

changedInput schema / properties / longitude / description

Previous value: -"Longitude coordinate"New value: +"Longitude in decimal degrees."

addedInput schema / properties / longitude / maximum
```
Added value: +180
```
addedInput schema / properties / longitude / minimum
```
Added value: +-180
```

changedInput schema / properties / parameters / description

Previous value: -"Comma-separated data parameters"New value: +"Comma-separated POWER parameters, e.g. T2M,PRECTOTCORR,WS10M."

addedInput schema / properties / parameters / pattern
```
Added value: +"^[A-Za-z0-9_]+(,[A-Za-z0-9_]+)*$"
```

changedInput schema / properties / start / description

Previous value: -"Start date (YYYYMMDD)"New value: +"Start date (YYYYMMDD)."

addedInput schema / properties / time_standard

Added value: +{
+  "description": "Time standard for daily values; POWER defaults to LST (local solar time) when omitted.",
+  "enum": [
+    "utc",
+    "lst"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "parameters",
-  "community",
-  "longitude",
-  "latitude",
-  "start",
-  "end"
-]New value: +[
+  "parameters",
+  "community",
+  "latitude",
+  "longitude",
+  "start",
+  "end"
+]

First observedAug 18, 2025

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds little beyond that—it does not mention timeouts, rate limits, or that the data is model-derived/reanalysis rather than observational. With annotations carrying the behavioral burden, a 3 is fair.

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 front-loaded sentence with zero filler that states the resource, granularity, and source. Nothing is wasted.

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 8 parameters and no output schema, the description is thin on what an agent receives back—no mention of returned fields, units, or response shape beyond 'daily'. The schema fully covers inputs, so this is adequate but not complete.

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%, with every parameter documented including enums for community, format, and time_standard. The description adds no parameter meaning (e.g., valid POWER parameter names, date range limits), so the baseline of 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?

The description names a specific resource (daily solar and meteorological data), its granularity (daily), and its scope (a point), plus expands the POWER acronym. It is clearly distinguishable from sibling tools, though it does not explicitly contrast itself with any of them.

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?

There is no when-to-use guidance, no mention of prerequisites such as which communities map to which parameter sets, and no indication of when an agent should prefer a different NASA dataset tool. Usage is only implied by the tool name and domain.

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

NASA POWER daily point data

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools