Skip to main content
Glama

wmshare_estimates

Retrieve analyst profit forecasts, detailed estimates, ratings, research reports, and financial disclosure schedules for a specified stock across CN, HK, or US markets.

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

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数上限
actionYes盈利预测/评级/研报/披露日动作
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
symbolNo标的代码;所有 action 都需要
max_rowsNo单次返回的最大行数,硬上限 200

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 says nothing about read-only vs mutating behavior, whether results are paginated, or the practical effect of the `output` modes (sample/count/summary) and `max_rows` cap. The only implicit signal is that 取 implies retrieval, which the agent must infer.

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 compact sentence with the resource scope front-loaded and no filler. The brevity is partly under-specification given a ten-value action enum, but the sentence itself is well formed and 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?

This is a multi-action dispatcher with ten enum values, no annotations, and six parameters; an agent needs to know which action yields which dataset to call it correctly. Since the output schema already covers return shapes, the missing piece is action semantics and any read-only/permission context, and the description supplies neither.

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 every parameter is already documented in the input schema, and the baseline of 3 applies. The description adds no meaning about how individual action values differ in the fields they return, which is the one thing the schema cannot express.

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 (取/get) plus a concrete list of resources: 盈利预测 (analyst forecasts), 预测明细 (forecast detail), 评级 (ratings), 研报 (research reports), 财报披露日程 (disclosure calendar). That is far more informative than the opaque name. It does not differentiate itself from plausible siblings such as wmshare_disclosures or wmshare_metrics, so it stops short of 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 Guidelines2/5

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

There is no guidance on when to use this tool versus the many related siblings, and nothing tells the agent how to pick among the ten `action` values (forecast vs forecast_detail vs yjkb vs yjyg are indistinguishable from the text). The description only enumerates data categories without mapping them to the required action selector.

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