Wudao A-Share Stock Data MCP

auction_opening_snapshot

Read-onlyIdempotent

一次返回六个固定竞价视图：竞价涨停、竞价跌停、涨停委买额前 N、竞价成交额前 N、昨日炸板今表现、昨日涨停今表现。每行保留完整竞价字段，适合开盘后快速复盘和生成观察名单。何时使用: 竞价全景快照：支持 snapshotTime=09:15/09:20/09:25，默认 09:25；早期尾秒指标不可用，买单对比仅返回已到时点。一次返回八个固定视图——竞价涨停、竞价跌停、涨停委买额前 N、竞价成交额前 N、9:25 尾秒抢筹、9:25 尾秒撤退、昨日炸板今表现、昨日涨停今表现；每行保留完整竞价字段。未传日期且今天非交易日时按交易日历查询上一交易日并标注实际日期；显式日期不自动换日。【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

Name	Required	Description
`limit`	No	六个全市场桶返回 top N：竞价涨停、竞价跌停、涨停委买额、竞价成交额、尾秒抢筹、尾秒撤退。默认 30，最大 100。
`format`	No	content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
`prevDate`	No	对比的昨日。不传则自动取 tradeDate 的上一交易日。
`excludeST`	No	是否剔除 ST/退市股，默认 true。
`tradeDate`	No	交易日期，支持 YYYY-MM-DD 或 YYYYMMDD。不传时：交易日取今日（所选时点尚未就绪返回 AUCTION_DATA_NOT_READY）；非交易日按交易日历取上一交易日并标注实际日期。显式日期不自动换日。
`detailLevel`	No	档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
`snapshotTime`	No	竞价截面时点，默认 09:25。09:15/09:20 复用工作台留存行情和涨停价买单；实际秒数、覆盖范围见 dataTiming。早期竞价额为虚拟撮合金额；不返回后续定盘字段。09:20 带相对 09:15 买单变化，显式 09:25 带三时点买单对比。
`prevPoolLimit`	No	昨日炸板今表现、昨日涨停今表现两个反馈池的返回上限。默认 200，最大 300。

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedInput schema / properties / snapshotTime

Added value: +{
+  "description": "竞价截面时点，默认 09:25。09:15/09:20 复用工作台留存行情和涨停价买单；实际秒数、覆盖范围见 dataTiming。早期竞价额为虚拟撮合金额；不返回后续定盘字段。09:20 带相对 09:15 买单变化，显式 09:25 带三时点买单对比。",
+  "enum": [
+    "09:15",
+    "09:20",
+    "09:25"
+  ],
+  "type": "string"
+}

changedInput schema / properties / tradeDate / description

Previous value: -"交易日期，支持 YYYY-MM-DD 或 YYYYMMDD。不传时：交易日取今日（9:25 前返回 AUCTION_DATA_NOT_READY）；非交易日按交易日历取上一交易日并标注实际日期。显式日期不自动换日。"New value: +"交易日期，支持 YYYY-MM-DD 或 YYYYMMDD。不传时：交易日取今日（所选时点尚未就绪返回 AUCTION_DATA_NOT_READY）；非交易日按交易日历取上一交易日并标注实际日期。显式日期不自动换日。"

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

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world. The description adds real behavioral context beyond them: trade-date fallback for non-trading days, the AUCTION_DATA_NOT_READY condition, dataTiming coverage, and that early-second indicators are unavailable at 09:15/09:20. That is substantive operational disclosure.

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 long and repetitive: it lists the fixed views twice with inconsistent counts (six then eight), duplicating the same enumeration. This redundancy wastes tokens and creates confusion rather than front-loading key constraints.

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. The description covers date resolution, non-trading-day fallback, readiness errors, timing caveats, and a link-format instruction — enough for an agent to call it correctly for a complex multi-parameter tool.

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 eight parameters, establishing the baseline of 3. The description restates snapshotTime and limit behavior but adds little syntax or format detail beyond the schema, and its 'six buckets' framing conflicts with the eight-view list.

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 verb+resource: returning a fixed set of opening-auction snapshot views with full auction fields. An agent knows it is the 'panorama' auction snapshot, distinct from auction_data or auction_market_scan. But the description internally contradicts itself, first claiming six fixed views and later eight, which muddies exactly what the tool returns.

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

Usage Guidelines3/5

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

Provides a '何时使用' line framing it as the panorama snapshot and lists the supported snapshotTime values with their data-availability caveats. However, it never names an alternative sibling (auction_data, auction_market_scan, auction_theme_strength) or states when NOT to use it, leaving routing to inference.

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.