SiteCheck Trade & Energy

Wind resource at a coordinate from NASA POWER: annual

energy_global_wind_atlas_data

Read-only

Wind resource at a coordinate from NASA POWER (MERRA-2 based 25-year climatology, ~0.5° grid): annual and monthly mean wind speed at 10 m and 50 m, prevailing direction at 50 m, the shear exponent between them, an extrapolated mean speed at your hub height and an estimated mean power density (Rayleigh distribution, air density 1.225 kg/m³). Coarse screening data; the Global Wind Atlas 250 m layers have no public point API. Related tools on this server, for a different need: energy_global_solar_atlas_pv when you need Global Solar Atlas long-term average solar resource at one. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "energy_global_wind_atlas_data"
  }
}

Input Schema

Name	Required	Description
`lat`	Yes	Latitude, -90 to 90
`lon`	Yes	Longitude, -180 to 180
`hubHeight`	No	Hub height in metres for the extrapolated speed, 10 to 250 (default 100)

Output Schema

Name	Required	Description	Default
`lat`	No
`lon`	No
`note`	No
`unit`	No
`period`	No
`source`	No
`checkedAt`	No
`hubHeightM`	No
`shearExponent`	No
`monthlyWindSpeed50m`	No
`annualMeanWindSpeed10m`	No
`annualMeanWindSpeed50m`	No
`estimatedMeanSpeedAtHub`	No
`prevailingDirection50mDeg`	No
`estimatedPowerDensityAtHubWm2`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only cover readOnly/openWorld; the description adds substantial context beyond them: data vintage and resolution, the extrapolation methodology and assumed air density, and a full commercial disclosure of $0.002 USDC per successful call via x402 across three chains with failed calls uncharged. Cost and billing semantics are exactly the behavior an agent needs before invoking a paid endpoint.

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?

A single dense paragraph, front-loaded with the resource and outputs before caveats, siblings, and pricing. Nearly every clause earns its place, though the run-on sentence mixing outputs, limitations, alternatives, and billing could be split for faster scanning.

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?

Return values are covered by the output schema, all three parameters are fully documented, provenance and accuracy caveats are stated, and payment mechanics are disclosed. Nothing an agent needs to decide or call correctly is missing for a paid read-only point lookup.

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 ranges and a default for hubHeight, so the schema already carries parameter meaning. The description reinforces that hubHeight drives the extrapolated speed and grounds it in the Rayleigh/1.225 kg/m³ method, but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

Names the exact resource and enumerates every returned quantity: annual/monthly mean wind speed at 10 m and 50 m, prevailing direction at 50 m, shear exponent, hub-height extrapolation, and Rayleigh-based power density. It also pins the provenance (NASA POWER / MERRA-2, 25-year climatology, ~0.5° grid) and explicitly distinguishes itself from the solar sibling, so an agent can select it without opening the schema.

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

Usage Guidelines4/5

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

"Coarse screening data" plus the note that Global Wind Atlas 250 m layers have no public point API tells the agent this is a screening-grade source, which implicitly excludes bankable micrositing. It also redirects to energy_global_solar_atlas_pv for a different need. No explicit 'do not use when' statement for wind alternatives, so short of a 5.

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

All SiteCheck Trade & Energy tools Inspect

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

Need Help?