Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

intraday_main_flow

Read-onlyIdempotent

查询盘中个股主力资金快照，支持自选股/指定代码池过滤。口径为开盘红盘中主力净额，不是传统四档大/中/小单资金流；用户问盘中主力、大单、竞价主力净额时优先使用。 何时使用: 盘中个股主力资金：开盘红口径，不是传统四档大/中/小单资金流。用户问自选股/指定股票盘中主力净额、大单净额、竞价主力净额时优先用它；不要改用 capital_flow。 【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

NameRequiredDescriptionDefault
codesNo可选。股票代码池，数组或逗号分隔字符串；适合传自选股/观察池后只看这些股票的盘中主力资金。
limitNo返回数量，默认 30，最大 300。
orderNo排序方向，默认 desc。desc
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
sortByNo排序字段，默认 mainNetAmount。可选 mainNetAmount/mainBuyAmount/mainSellAmount/auctionMainNetAmount/auctionMainBuyAmount/auctionMainSellAmount。mainNetAmount
keywordNo可选。股票名称或代码关键词过滤。
tradeDateNo交易日期，支持 YYYY-MM-DD 或 YYYYMMDD。不传默认最近交易日/今日盘中缓存。
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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so safety is covered. The description adds real behavioral value by defining the measurement caliber (开盘红 main-net, not the traditional four-tier order flow) and the required markdown link format for listed stocks — context not present in structured fields. Pagination/rate behavior is not discussed, but the output schema exists.

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?

Purpose is front-loaded, but the caliber clause ("开盘红...不是传统四档大/中/小单资金流") is stated twice — once in the opening and again inside 何时使用 — which is redundant. The link-format note is useful, yet the overall text could be tightened without losing meaning.

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 not be explained, and annotations cover the safety profile. The description still conveys purpose, trigger conditions, the key alternative to avoid, and the caliber distinction, leaving little essential information missing apart from minor efficiency/detail notes.

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 (codes, limit, order, format, sortBy, keyword, tradeDate, detailLevel). The description echoes the codes filter use case but adds no per-parameter syntax or defaults beyond the schema, making this the baseline 3.

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?

The description gives a specific verb+resource ("查询盘中个股主力资金快照") plus an explicit scope qualifier ("口径为开盘红盘中主力净额"). It directly contrasts itself with the sibling capital_flow, so an agent can disambiguate without opening either schema.

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?

There is an explicit "何时使用" section naming the trigger scenarios (盘中主力净额、大单净额、竞价主力净额) and a when-NOT clause ("不要改用 capital_flow"). The routing instruction is 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