Skip to main content
Glama

wmshare_metrics

Validates metric codes then batch-fetches current values for multiple indicators of one stock symbol across CN, HK, or US markets, with sample, count, or summary output.

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": {
      "symbol": "<symbol>",
      "codes": "<codes>"
    },
    "name": "wmshare_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
codesYes离线目录中真实存在的指标码;先 search 再调用
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
symbolYes标的代码
max_rowsNo单次返回的最大行数,硬上限 200

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full load, yet it discloses only one behavioral trait: codes are validated before retrieval. It does not say what happens when a code is invalid (error, skipped, partial result), whether the call is read-only, how market defaults are resolved, or how the 200-row cap affects results. For an unannotated tool this leaves significant behavioral gaps.

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?

It is a single front-loaded sentence with no filler, and the validation precondition comes before the fetch action. It is efficient, though so terse that the price of conciseness is missing context rather than wasted words.

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?

An output schema exists, so return values need not be explained, and the schema covers all parameters. Still, with no annotations and five parameters, the description should at least clarify the relationship to other retrieval tools and what happens to invalid codes; as written, it is adequate but incomplete.

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 100%, so all five parameters, including the market enum, output modes, and max_rows cap, are already documented in the schema. The description only reinforces that symbol is a single instrument and codes is a set of metrics, adding no new semantics. Baseline 3 applies.

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 and resource: batch-fetch current values of several metric codes for a single instrument, with a code-validation step first. An agent can tell this is a multi-metric snapshot lookup rather than a search or history call. It does not explicitly distinguish itself from sibling tools such as wmshare_batch or wmshare_history, which keeps it from 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 description implies a use sequence: validate the codes, then fetch, and the codes parameter repeats 'search first'. However, it never states when to choose this over wmshare_history (time series) or wmshare_batch, and gives no exclusion or precondition guidance at the tool level.

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