Skip to main content
Glama

Antigravity x402 & MCP Gateway

compute_wind_lcoe_and_eya

[0.005000 USDC via x402] Computes IEC-grounded Weibull P50/P75/P90 net annual energy production (MWh) with RSS uncertainty and exact Decimal project finance metrics (Total CAPEX, LCOE $/MWh, NPV, Project IRR %, Min P90 DSCR).

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": {
      "capacity_mw": "<capacity_mw>"
    },
    "name": "compute_wind_lcoe_and_eya"
  }
}

Input Schema

NameRequiredDescriptionDefault
weibull_kNoWeibull shape parameter k between 1.2 and 4.0 (default '2.1').
capacity_mwYesInstalled wind farm nameplate capacity in MW (0.5 to 5000).
project_yearsNoOperating project lifetime in years between 5 and 35 (default 20).
wake_loss_pctNoArray wake loss percentage between 0 and 30 (default '7.5').
capex_usd_per_kwNoTotal installed CAPEX in USD per kW (default '1350').
discount_rate_pctNoNominal WACC / discount rate percentage (default '8.0').
mean_wind_speed_msNoHub-height annual mean wind speed in m/s (default '7.8').
opex_usd_per_kw_yrNoAnnual O&M OPEX in USD per kW-year (default '36').
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.005000 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

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the paid nature (0.005 USDC via x402) and names the computed outputs, which is genuinely useful. It does not say whether results are deterministic, whether payment is per-call, what happens on invalid inputs, or that omitting the signature returns a quote — that last point lives only in the schema.

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?

One dense sentence, front-loaded with the payment cost and then the outputs. No filler, no restatement of the tool name, and every clause carries information.

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?

There is no output schema, so the description's enumeration of returned metrics does real work. However, for a 10-parameter financial model with no annotations, it leaves out how the tool relates to its nearest sibling and any caveats about the model's assumptions.

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%, so every parameter already has ranges and defaults documented. The description adds no parameter-level meaning (e.g. which inputs drive uncertainty, or the relationship between wake loss and net AEP) beyond what the schema provides, so the baseline 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?

States a specific verb+resource pair (computes wind LCOE and net annual energy production) and enumerates the concrete outputs (P50/P75/P90 MWh, CAPEX, LCOE, NPV, IRR, DSCR). It is distinguishable from most siblings on subject matter, though it never explicitly contrasts with the close sibling assess_live_wind_eya.

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 when-to-use or when-not-to-use guidance is given. An agent facing assess_live_wind_eya versus compute_wind_lcoe_and_eya must infer the difference entirely from the names, and nothing states prerequisites such as having a valid site wind resource or how the two tools relate.

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.