Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

theme_intraday_capital

Read-onlyIdempotent

题材/板块强度与主力资金主入口：默认返回最新快照；mode=timeline 可返回精选题材、概念或行业的盘中资金曲线。问爆发原因/为何走强时传 includeBoomReason=true 读 boomReason。成分股下钻请用 theme_stocks。 何时使用: 题材/板块主入口：盘中板块强度与主力资金排行。问"为什么这个板块强/爆发逻辑"时传 includeBoomReason=true 读取 rows[].boomReason（冷门板可能为空，勿编造）。成分下钻用 theme_stocks。不要用 capital_flow(sector) 或已隐藏的 concept_ranking。

Input Schema

NameRequiredDescriptionDefault
modeNo返回模式。snapshot=最新快照；timeline=分钟级板块资金曲线。snapshot
limitNo返回数量。snapshot 默认 30、最大 100；timeline 最大 10。
orderNo排序方向，默认 desc。desc
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
sortByNo排序字段，默认 mainNetAmount。可选 mainNetAmount/bigOrderNetAmount/strength/pctChg/changeSpeed/amount/volumeRatio。mainNetAmount
endTimeNotimeline 可选结束时间，HH:mm。
keywordNo可选。板块名称或代码关键词过滤。
baselineNotimeline 金额基准。open=相对首个时点变化；raw=原始累计净额。open
universeNo板块范围。featured=精选题材；concept=完整概念；industry=行业。featured
startTimeNotimeline 可选起始时间，HH:mm。
tradeDateNo交易日期，支持 YYYY-MM-DD 或 YYYYMMDD。不传默认最近交易日/今日盘中缓存。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
themeSymbolsNo可选。板块代码过滤，数组或逗号分隔字符串。
intervalMinutesNotimeline 模式的采样间隔，默认 5 分钟。
includeBoomReasonNo是否附加开盘啦板块爆发原因（rows[].boomReason/boomTitle/boomLeaders）。默认 false。用户问"为什么这个板块强/爆发逻辑/催化"时再开；冷门板可能为空，勿编造。

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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds useful operational context beyond that: default snapshot behavior, that boomReason can be empty on obscure boards ('冷门板可能为空，勿编造'), and output shape hints (rows[].boomReason). This is value-add over the annotations, though it doesn't discuss rate limits or pagination.

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?

Front-loaded with the core purpose and scoping, and structured with a clear usage block. However, the theme_stocks drill-down and the includeBoomReason instruction are each stated twice, which is avoidable duplication for a definition of this length.

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?

Output schema exists and annotations are rich, so return-shape detail isn't required. The description covers mode selection, the boomReason opt-in, and routing to siblings, leaving the 15-param surface adequately handled by the fully-covered schema.

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 every parameter carries an inline enum/default/description, so the schema does the heavy lifting. The description echoes mode=timeline and includeBoomReason semantics but adds no syntax or format detail beyond what the schema already states, so 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+resource ('题材/板块强度与主力资金主入口') and immediately names scope (snapshot vs timeline) plus the drill-down sibling theme_stocks. An agent can distinguish it from capital_flow and concept_ranking without opening any other definition.

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?

A dedicated '何时使用' section tells the agent this is the sector/theme main entry, gives the condition for includeBoomReason=true, names theme_stocks for constituent drill-down, and explicitly excludes capital_flow(sector) and the hidden concept_ranking. When/when-not/alternatives are all explicit.

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