Skip to main content
Glama

wmshare_corporate

Query corporate governance and ownership data including shareholders, capital changes, pledges, buybacks, executive changes, guarantees, litigation, violations, and institutional holdings for a stock.

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_corporate"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数上限
actionYes公司治理/股权/质押/增减持动作
annualNo*_at 查询的年报年度,如 2024
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
symbolNo标的代码;全市场质押汇总 actions 可空
max_rowsNo单次返回的最大行数,硬上限 200
samplingNo*_at 查询的报告期采样,如 Q4

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 of behavioral disclosure and does not meet it: it says nothing about read-only semantics, permission or market-scope requirements, rate limits, or the fact that 'action' selects among 26 distinct sub-queries. It also omits the sample/count/summary output modes and the 200-row hard cap, both of which materially change the call shape.

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 economical sentence with no filler and the resource enumeration front-loaded. It is arguably too terse rather than padded — the brevity comes at the cost of routing guidance and behavioral detail.

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?

For a tool with 26 action values, 8 parameters, and a multi-market scope, the description is thin: it never explains the action-dispatch model, the meaning of landmark-derived fields, or how market defaulting works. The output schema and full schema coverage offset some of this, keeping it at minimum-viable rather than inadequate.

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 schema already documents all 8 parameters at 100% coverage, including the 26-value action enum, market enum, and output mode, so the baseline of 3 is lifted slightly because the description's topic list loosely hints at which action families exist (pledge, buyback, holder, litigation). It still contributes no syntax, defaults, or interaction rules beyond what the schema states.

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 (取/get) plus a concrete set of resources — shareholders, share capital, pledges, buybacks, executives, litigation, institutional holdings — which lets an agent infer this is the corporate-governance/equity data tool. It does not distinguish itself from siblings such as wmshare_dividend or wmshare_statement, and it never mentions that the tool is action-dispatched, so the enumeration reads as a topic list rather than a capability statement.

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, no when-not-to-use guidance, and no named alternative among the ~20 sibling tools. An agent must guess whether a dividend or equity-change question belongs here or in wmshare_dividend.

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