Wudao A-Share Stock Data MCP

capital_flow

Read-onlyIdempotent

资金流向：个股/大盘/北向=东财日频四档；盘中个股主力用 intraday_main_flow；板块资金请优先 theme_intraday_capital（本工具 flowType=sector 仅兼容，东财板块传 sectorSource=dongfang）何时使用: 资金流：个股/大盘/北向=东财日频四档。板块资金请直接用 theme_intraday_capital；本工具 flowType=sector 仅兼容（默认等同 theme_*，东财板块传 sectorSource=dongfang）。盘中个股主力用 intraday_main_flow。【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

Name	Required	Description	Default
`date`	No	交易日期，支持 YYYY-MM-DD 或 YYYYMMDD；可选。个股/大盘/北向与东财板块为日频资金流；开盘啦板块为盘中题材资金快照日期。
`limit`	No	返回数量，默认 10。
`format`	No	content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
`keyword`	No	可选。flowType=sector 且开盘啦口径时，按题材名/代码模糊过滤。
`flowType`	No	资金流类型，默认 market。stock=个股，sector=板块，market=大盘，hsgt=沪深港通/北向。	market
`stockCode`	No	flowType=stock 单股查询：代码或名称，例如 600519、贵州茅台。
`sectorType`	No	仅 sectorSource=dongfang 时有效：板块类型，默认概念。常用：概念、行业、地域。	概念
`stockCodes`	No	flowType=stock 批量查询：代码或名称数组，例如 ["600519","000001"]。上限 20 只。多股资金流横向比较时优先用 stockCodes。
`detailLevel`	No	档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
`sectorSource`	No	【兼容】板块资金请优先直接调 theme_intraday_capital。本参数仅在 flowType=sector 时有效：默认 kpl 内部复用 theme_*；dongfang/dc=东财日频 moneyflow_ind_dc。	kpl

Output Schema

Name	Required	Description	Default
`data`	No
`meta`	No
`success`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

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。"

Changed1 schema field changedOct 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {},
+    "meta": {},
+    "success": {}
+  },
+  "type": "object"
+}

First observedOct 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety behavior is covered. The description adds the 'linkage' requirement about markdown link formatting for stock mentions, which is behaviorally relevant output formatting guidance. However it doesn't disclose return structure details beyond what the output schema would carry. With annotations covering safety, a 3 is appropriate.

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

Conciseness2/5

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

The description is repetitive: the 何时使用 block restates the same routing information given in the first sentence almost verbatim (板块资金请优先 theme_intraday_capital / 盘中个股主力用 intraday_main_flow appear twice). The markdown-link instruction is buried at the end. This is bloated and not front-loaded.

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 complex 10-param tool with an output schema, the description covers routing, scope, and the important output formatting requirement (markdown links). Since a schema exists it needn't explain return values, and safety annotations cover the rest. The redundancy means the information is present, just not efficiently structured.

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 baseline is 3. The description's narrative about flowType=sector compatibility and sectorSource=dongfang aligns with but largely restates schema enum descriptions. It adds context on the compatibility path but doesn't introduce semantics beyond the schema.

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 states a specific verb+resource: fetching capital flow data, with coverage scope (个股/大盘/北向 as 东财日频四档). It explicitly names sibling tools (intraday_main_flow, theme_intraday_capital) and identifies this tool's scope vs. them. Not quite a 5 because the purpose statement is densely embedded in routing guidance rather than cleanly front-loaded.

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?

Explicit when-to-use rules with named alternatives: 盘中个股主力用 intraday_main_flow, 板块资金优先 theme_intraday_capital, and this tool's flowType=sector exists only for compatibility. It specifies the exception condition (sectorSource=dongfang) for East Money sector data. This is textbook routing guidance.

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 tools Inspect

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.