Skip to main content
Glama

wmshare_intl

Retrieve CCASS, major shareholder, analyst rating, earnings forecast, short-selling, or US issuance data for Hong Kong and US stocks by symbol.

Instructions

取 CCASS、主要股东、评级、盈利预测、沽空或美股发行信息;market 必须 hk/us。

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>",
      "symbol": "<symbol>"
    },
    "name": "wmshare_intl"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数上限
actionYes港美股专项动作
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

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 behavioral burden. The verb 取 (fetch/retrieve) implies a read-only lookup, but the description says nothing about permissions, rate limits, pagination behavior, or what the output modes mean in practice, leaving the agent to infer the safety profile.

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?

One compact sentence plus a constraint clause, with the resource list front-loaded and no filler. It is arguably too terse for a six-parameter tool, but nothing 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?

With six parameters, two enums, no annotations, and an output schema present, the definition is minimally adequate: the output schema covers return values and the input schema covers parameters. However, the relationship among the six actions and the meaning of the sample/count/summary output modes relative to each action remains unexplained.

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 the enum options and defaults for action, output, limit, and max_rows are already documented, which sets the baseline at 3. The description does add that symbol is an HK/US ticker, but its claim that market must be hk/us conflicts with the schema enum that also permits 'cn', creating ambiguity rather than clarity.

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 concrete resources it retrieves — CCASS, major shareholders, ratings, earnings forecasts, short selling, and US issuance data — which maps one-to-one onto the six-value action enum. An agent can tell what it fetches, but nothing distinguishes it from overlapping siblings such as wmshare_estimates or wmshare_market.

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 explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The only routing hint is 'market 必须 hk/us' (market must be hk/us), which tells the agent the market scope but not how to choose this tool over the many sibling tools covering overlapping data.

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