Skip to main content
Glama

wmshare_dividend

Retrieve dividend history, DPS, TTM yield and payout metrics, window statistics, and screen stocks by dividend quality, yield, payout, and valuation thresholds across CN/HK/US markets.

Instructions

取分红历史、DPS、TTM 指标、窗口统计和质量筛选;率值均为小数。

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": {
      "action": "<action>"
    },
    "name": "wmshare_dividend"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo日期,格式 YYYY-MM-DD
beginNo日期,格式 YYYY-MM-DD
limitNohistory 返回条数
actionYes分红动作
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
symbolNo标的代码;所有 action 都需要
windowNowindow_stats 窗口,如 3y/5y3y
min_pctNo低估高分红的估值分位门槛,小数
max_rowsNo单次返回的最大行数,硬上限 200
min_yieldNo最低股息率,小数;0.03=3%
payout_maxNo派息率上限,小数
payout_minNo派息率下限,小数

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 burden, yet it only discloses one behavioral fact: that rate values are decimals. It never states that the tool is a read-only lookup with no side effects, nor does it mention the hard 200-row cap, the output-mode tradeoffs, or that a missing market falls back to server config — all of which materially affect how an agent calls it.

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?

A single front-loaded sentence that lists capabilities first and appends the unit convention, with no filler. It is efficient, though the terse list format leaves no room for the routing information an agent actually needs.

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 no explanation, and the 13-parameter schema is fully annotated. But for a nine-action tool, the description gives no per-action guidance on required inputs or parameter interactions, leaving a meaningful gap relative to the tool's complexity.

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 13 parameters are already documented, and the description's only added semantics — rates expressed as decimals — largely repeats what the schema says for min_yield ('0.03=3%') and min_pct. Baseline 3 applies when the schema does the heavy lifting and the description adds little beyond it.

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 the resource (dividends) and enumerates the concrete capability set — history, DPS, TTM metrics, window statistics, and quality screening — which maps closely onto the action enum. It does not, however, distinguish this tool from siblings like wmshare_screen or wmshare_metrics, so an agent cannot tell from the text alone why it should pick this tool over those.

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: nothing says which action to pick for which intent, that symbol is required for every action, that screening actions need the min_yield/payout thresholds, or that market defaults to a server-configured value. The reader must infer the entire action-selection logic from enum names in the schema.

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