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

天机气象 · 电力提示 MCP

by txZheng

power_weather_hint

Generates location-specific power-weather advisories for wind, solar, and grid use, merging high-wind, icing, temperature, heavy-rain, and cloud events with trigger thresholds.

Instructions

指定点位的电力气象提示:大风/覆冰/低温/高温/强降水/云遮挡,按事件合并并给出触发条件。scenario 可选 wind(风电)/pv(光伏)/grid(电网)/general。

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": "power_weather_hint"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNo
cut_outNo
locationYes
scenarioNogeneral
start_hourNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 behavioral burden. It does disclose that events are merged by type and that trigger conditions are returned, which is useful output-behavior context, but it says nothing about data source, permissions, rate limits, latency, or how the look-ahead window is applied.

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?

Two compact sentences: the first front-loads what is produced, the second covers the scenario selector. Little wasted wording, though the hazard list could be shortened and the definition stops short of the details an agent actually needs.

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

Completeness2/5

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

For a five-parameter tool with no annotations and no output schema, the description is thin. It omits location format, time-window behavior, the meaning of cut_out, and any indication of the response shape, leaving significant gaps an agent would have to guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 explain all five parameters; it only explains scenario's allowed values. location format (coordinates vs. station id), hours/start_hour window semantics, and especially cut_out (a 25 m/s default threshold that is meaningless without context) are left entirely undocumented.

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 (power-meteorological hints for a given location) and enumerates the hazard types it reports (high wind, icing, low temperature, high temperature, heavy precipitation, cloud blocking) plus the event-merging behavior. This is far more specific than the bare tool name, though it does not explicitly contrast itself with siblings like theoretical_power or wind_solar_snapshot.

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 scenario enumeration (wind/pv/grid/general) implies which asset context to pick, which gives an agent implied usage guidance. However, there is no explicit statement of when to choose this tool over the sibling power tools, nor any prerequisite or exclusion conditions.

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