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

天机气象 · 电力提示 MCP

by txZheng

get_dataset

Fetch all authorized hourly forecast data for a location and time window without server-side filtering. Use field projection and row limits to control the returned dataset while the full cache remains available to other tools.

Instructions

唯一的取数入口:返回该窗口内全部已授权要素(服务端不支持筛选,故一次取全)。其他加工类工具会复用同一份缓存,不需要先调用本工具。fields 可选,用于投影列;limit>0 时只截断本次返回的行数,不影响缓存与其他工具计算所用的完整数据。

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

Input Schema

NameRequiredDescriptionDefault
hoursNo
limitNo
t_resNo1h
fieldsNo
locationYes
start_hourNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses meaningful traits: the server cannot filter so everything in the window is returned, authorization scoping applies, and results are cached and shared. It omits return format, pagination and size/rate expectations.

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?

Front-loaded with the core identity and constraints, and the limit/cache caveat is stated precisely. Some density and the bolded emphasis are minor costs, but no sentence is wasted.

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?

No output schema and no annotations mean the description must cover both safety and results, and it covers behavior well but leaves four of six parameters and the meaning of 'the window' unexplained, so an agent cannot construct a correct call from it alone.

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 coverage is 0% across 6 parameters, and the description only explains two of them (fields for column projection, limit as a return-only truncation that does not affect the cache). The window parameters (hours, start_hour, t_res) and location, which define the core selection semantics, are entirely undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('取数入口' returning '全部已授权要素' within a window) and explicitly positions itself as the sole data-fetch entry point relative to the processing siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear when-not rule: processing tools reuse the same cache, so this need not be called first. It lacks an explicit statement of when an agent should call it (e.g., when it needs raw rows for its own inspection versus delegating to a processing tool).

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