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

天机气象 · 电力提示 MCP

by txZheng

wind_solar_snapshot

Returns hourly snapshots of hub-height wind speed, dew point, wind level, and related weather elements for a location, helping assess short-term wind and solar power conditions.

Instructions

风电/光伏关心的关键要素逐时快照(含轮毂风速、露点、风力等级等派生量)。

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

Input Schema

NameRequiredDescriptionDefault
hoursNo
t_resNo1h
locationYes
start_hourNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that derived quantities are included, which is useful, but says nothing about data source, units, timezone handling, caching, rate limits, or whether the call is read-only — all of which matter for a 4-parameter data-fetch tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with the core purpose front-loaded and no wasted words. However, the brevity comes at the cost of under-specification rather than being genuinely efficient.

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?

With no annotations, no output schema, and four completely undocumented parameters, the description leaves too much unknown for an agent to invoke the tool confidently. It should at minimum explain the time-window parameters and the location format.

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% and all four parameters (location, hours, t_res, start_hour) are undocumented in the schema. The description only hints at hourly resolution via '逐时', giving no meaning for hours, start_hour, t_res, or the expected location format, so it fails to compensate for the coverage gap.

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 verb+resource: an hourly snapshot of key wind/solar power elements, and enumerates representative derived quantities (hub wind speed, dew point, wind force level). It is clear what the tool returns, but it never distinguishes itself from siblings such as power_weather_hint or theoretical_power, so an agent cannot tell which to pick from the text alone.

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?

There is no when-to-use guidance, no mention of when not to use it, and no reference to any alternative tool. The agent must infer from the name and sibling list that this is the raw hourly weather snapshot versus the hint/power-calculation tools.

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