Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

dragon_tiger

Read-onlyIdempotent

龙虎榜买卖席位详情。按游资名/营业部追踪请用 branchSearch（不要用 stockName），如 branchSearch="炒股养家" 会通过 BranchTag 反查自动扩展到对应营业部；startDate+endDate 支持区间扫描（如某游资最近一周操作轨迹）；stockCode 查个股席位。 何时使用: 龙虎榜席位和机构/活跃资金。重要：「按游资名/营业部追踪」必须用 branchSearch 参数，不要用 stockName（stockName 只搜股票名）。例：查"炒股养家最近一周操作"用 branchSearch="炒股养家"+startDate/endDate（支持 BranchTag 标签反查，会自动扩展到对应营业部）；查"三亚迎宾路上榜没"用 branchSearch="三亚迎宾路"；查"某票谁在做"用 stockCode。配合 limit_up_ladder。 【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

NameRequiredDescriptionDefault
dateNo龙虎榜日期，格式 YYYY-MM-DD。与 startDate/endDate 二选一。
pageNo页码，默认 1。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
endDateNo区间结束日期。
pageSizeNo每页数量，默认 50，最大 100。
startDateNo区间开始日期。追踪某游资近期操作时和 endDate + branchSearch 配合使用。
stockCodeNo股票代码或名称。
stockNameNo股票名称关键词（只搜股票）。注意：搜游资/营业部请用 branchSearch，不要用这里。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
branchSearchNo【按游资/营业部搜索请用这个，不是 stockName】关键词支持：①营业部名称（如"东方财富证券拉萨"、"三亚迎宾路"）；②BranchTag 游资名/标签（如"炒股养家"、"一线游资"、"溧阳路"），后端会反查所有打了该 tag 的营业部并一起搜。配合 startDate+endDate 追踪某游资近期操作轨迹。

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond them: the BranchTag reverse-lookup that auto-expands a 游资 name to its constituent 营业部, the date-range scan behavior, and a mandatory markdown-link output convention. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The branchSearch-vs-stockName warning is repeated three times in slightly different wording, and the BranchTag expansion is explained twice. The core instruction is front-loaded, but the redundancy inflates length without adding information an agent needs.

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?

For a 10-parameter, zero-required tool with a full output schema, the description covers the key selection paths (branch/stock/date-range), output formats, and the link-formatting requirement, so the agent can invoke it correctly. Return values are rightly left to the output schema. No critical gap remains.

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%, and the branchSearch schema field already documents the BranchTag reverse-lookup and keyword types, so the description largely restates it. It adds only marginal meaning (pairing branchSearch with startDate/endDate, stockCode vs stockName), which justifies the baseline-3 rather than a higher score.

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?

States a specific resource and scope: '龙虎榜买卖席位详情' (dragon-tiger list buy/sell seat details), and explicitly distinguishes its two search modes (游资/营业部 via branchSearch vs 个股 via stockCode). The intent is clear, though the point is buried inside dense, repetitive prose rather than a crisp opening line.

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

Usage Guidelines5/5

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

Explicitly covers when to use ('何时使用: 龙虎榜席位和机构/活跃资金'), when NOT to use a parameter ('按游资名/营业部追踪必须用 branchSearch，不要用 stockName'), and names an adjacent sibling ('配合 limit_up_ladder'). Worked examples ('炒股养家最近一周操作', '三亚迎宾路上榜没') make the selection criteria unambiguous.

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