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

天机气象 · 电力提示 MCP

by txZheng

get_capability

Check authorized weather elements, known data gaps, call budget, and endpoints before making requests to avoid wasting API quota.

Instructions

查看已授权要素、已知不可用要素、调用预算与端点。开工前先调用它,避免浪费额度。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_capability"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Because no annotations are provided, the description has to carry the whole behavioral burden, and it does disclose the categories of information the tool returns. However, it never says whether the tool is a read-only probe or whether calling it itself draws down the budget, and it does not say whether the results are cached or whether they change over time. The phrase 'avoid wasting quota' implies the tool is a cheap preflight check, but it does not state that explicitly.

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?

This is a tight two-sentence definition whose first sentence lists what the tool reveals and whose second sentence gives the call timing and the rationale, in that order, with no wasted wording.

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

Completeness4/5

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

The tool is simple: it takes no parameters, has no annotations, and has no output schema. The description usefully explains what the tool returns (authorized features, unavailable features, budget, endpoints) and when to call it, which together are enough for an agent to use the tool. It could be better if it clarified whether the tool's results are static or scoped to a session, and whether the tool itself consumes budget.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so parameter semantics reach the baseline of 4; the schema has 100% description coverage and there is nothing for the description to document. Here the description cannot add any meaning beyond the schema, and it does not need to.

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 gives a specific verb (查看/view) over a concrete set of resources: authorized features (已授权要素), features known to be unavailable (已知不可用要素), the call budget (调用预算), and endpoints (端点). Its purpose is therefore clear, though it never names a sibling tool to contrast with, so it stops short of 5.

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?

The definition states a timing condition (before starting work / 开工前先调用它) together with the reason that motivates it (to avoid wasting quota / 避免浪费额度). That gives clear guidance on when to use the tool, although it does not say when not to use it or which sibling tool it is to be preferred over.

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