Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

shareholder_structure

Read-onlyIdempotent

聚合十大股东、十大流通股东、股东户数、质押、分红和回购数据，观察筹码和公司行为 何时使用: 十大股东、户数趋势、质押、分红、回购；配合 valuation_snapshot。

Input Schema

NameRequiredDescriptionDefault
codeYes必填。股票代码或名称。
limitNo十大股东/流通股东返回数量，默认 10，最大 30。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
endDateNo可选。区间结束日期；默认今天。
sectionsNo可选展开：top10/floatHolders/holderNumbers/pledge/dividends/repurchases/all。不传=top10+holderNumbers。
startDateNo可选。区间开始日期；默认近三年。
embedStockNo是否回完整 stock 档案（行业/地区/交易所等）。不传=false。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。

Output Schema

NameRequiredDescriptionDefault
dataNo
metaNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / detailLevel / description
      Previous value: -"输出详细度（不传=standard，返回 Agent 可计算标准字段）。summary=压缩摘要；raw=全字段+原始数据。"New value: +"档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。"
    • changedInput schema / properties / format / description
      Previous value: -"content[0].text 形态。通常不传=1 行 headline；auction_market_scan / auction_theme_strength 在 standard/raw 档默认直接返回 JSON 明细。markdown=完整 markdown 表格；json=完整 JSON。"New value: +"content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {},
+    "meta": {},
+    "success": {}
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds the aggregation scope and the analytical intent ('观察筹码和公司行为') but no rate limits, auth needs, or mutation/caching caveats beyond what annotations provide.

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?

Purpose is front-loaded and the two-sentence structure is economical. The missing punctuation between the data list and '何时使用' slightly blurs the boundary, but there is no wasted content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the description covers both aggregation scope and usage triggers for an 8-param tool. Nothing critical is missing, though it could say more about how sections/defaults shape the response.

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 schema already documents all 8 parameters including defaults and valid ranges. The description's mention of the same categories adds no syntax or format detail beyond the structured fields, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (聚合/aggregate) plus the exact resource categories it covers (十大股东, 流通股东, 户数, 质押, 分红, 回购), so the agent immediately knows the tool's scope. The enumerated data families also distinguish it from siblings like valuation_snapshot or official_disclosure_evidence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Contains an explicit '何时使用' section listing triggers (top-10 holders, holder-count trends, pledge, dividends, buybacks) and names a companion tool (valuation_snapshot). It stops short of stating exclusions or true alternatives, but the usage context is clear.

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

All Wudao A-Share Stock Data MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources