Skip to main content
Glama
天机气象 · 电力提示 MCP

天机气象 · 电力提示 MCP

by txZheng

theoretical_power

Estimates demonstrative wind or PV theoretical power for a location and time window from weather data, applying wind power curves or PV irradiance, performance ratio, and temperature corrections.

Instructions

理论出力演示(非功率预测)。kind=wind 按功率曲线把风速映射为出力,切入/额定/切出、轮毂高度、容量、自定义 curve 均可指定;kind=pv 按辐照度×性能比×温度修正算光伏出力,pr/tilt_gain 可指定。

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": {
      "location": "<location>"
    },
    "name": "theoretical_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
prNo
kindNowind
curveNo
hoursNo
ratedNo
cut_inNo
cut_outNo
locationYes
tilt_gainNo
hub_heightNo
start_hourNo
capacity_mwNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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, and it does disclose the actual computation for both modes (power-curve mapping for wind; irradiance × performance ratio × temperature correction for PV). It does not state that this is a side-effect-free pure calculation, nor what the response contains (time series? single value? units?) for a 12-parameter tool.

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 dense sentence pair: purpose and the forecasting caveat come first, then a clause per mode listing only the knobs that matter. No filler, nothing repeated from the schema, and the mode split is easy to scan.

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?

For a 12-parameter computation tool with no annotations and no output schema, the description covers the algorithmic behavior well but leaves the required 'location' input and the time-window parameters (hours, start_hour) undefined, and gives no hint of return shape or units. Adequate but with clear gaps an agent would hit on first call.

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 0%, so the description must compensate, and it does explain kind, curve, cut_in/rated/cut_out, hub_height, capacity_mw, pr and tilt_gain. Critically, the required parameter 'location' is never mentioned, and hours/start_hour go unexplained, and no units are given for rated, hub_height or capacity_mw.

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 opens with a precise verb+resource statement ('理论出力演示', theoretical output demonstration) and explicitly excludes forecasting ('非功率预测'), which is exactly the distinction an agent needs versus the weather/forecast siblings. It then splits into the two supported modes (kind=wind, kind=pv). It does not name a specific sibling tool, keeping it just short of a 5.

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 parenthetical '非功率预测' tells the agent what this is NOT, which implicitly steers use toward demonstration/sizing scenarios rather than live forecasting. However, no sibling is named and there is no explicit 'use X instead when...' rule, so the agent must infer routing from the negative hint alone.

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