Skip to main content
Glama

Antigravity x402 & MCP Gateway

assess_live_wind_eya

[0.008000 USDC via x402] Fetches live hourly 100m wind speed, temperature, and pressure for any global (latitude, longitude), applies IEC 61400-12 shear & air-density scaling to hub height, fits Weibull k, and computes P50/P90 AEP & LCOE.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "assess_live_wind_eya"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYesSite WGS84 latitude between -90 and 90 (e.g., 10.60).
longitudeYesSite WGS84 longitude between -180 and 180 (e.g., 106.85).
capacity_mwNoPlanned wind farm nameplate capacity in MW (default '50').
hub_height_mNoTurbine hub height in meters between 40 and 220 (default 120).
ppa_price_usd_per_mwhNoPower Purchase Agreement tariff in USD per MWh (default '78.0').
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.008000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose the key behavioral traits: a fixed 0.008000 USDC x402 charge, and that omitting the payment signature returns a live quote instead of results. It also reveals the full processing pipeline, which tells an agent what the output will contain. It stops short of failure modes, data-source latency, or rate-limit behavior.

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 sentence with no filler, and the pricing marker is front-loaded so cost is visible before anything else. It is dense to the point of being jargon-heavy (IEC 61400-12, Weibull k, P50/P90 AEP & LCOE), which costs some readability, but nothing is redundant.

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

Completeness4/5

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

For a six-parameter tool with fully documented schema and no output schema, the description covers cost, inputs consumed, and the derived outputs (P50/P90 AEP & LCOE) an agent would want before calling. The remaining gap is that it never explains when to prefer the alternative wind tool.

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%, including ranges, defaults, and the x402 signature/payment-chain detail, so the schema already does the parameter work. The description adds only that the coordinates drive a global site lookup and that hub height participates in the shear scaling; it adds no new meaning to capacity_mw or ppa_price beyond what the schema states.

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?

Names a specific verb chain and resource: fetches live hourly 100m wind speed/temperature/pressure for a lat/lon, then applies IEC 61400-12 shear and air-density scaling, fits Weibull k, and computes P50/P90 AEP and LCOE. That is clearly distinguishable from a pure-calculation sibling, though it never names the sibling it differs from.

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 word 'live' implies this is the tool for real, current site conditions as opposed to a purely computational AEP/LCOE tool, but the description never states the condition that selects this over compute_wind_lcoe_and_eya, nor any prerequisites or exclusions. Usage is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.