Wudao A-Share Stock Data MCP

limit_events

Read-onlyIdempotent

实时推送涨停封板和炸板事件，精确到秒级时间戳，适合盘中监控何时使用: 秒级封/炸事件流。仅当用户明确要求实时事件或最新封板时使用，否则用 limit_up_ladder。【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

Name	Required	Description	Default
`type`	No	事件类型，当前仅支持 limit_up 封板/炸板事件。跌停池请使用 limit_down 工具。	limit_up
`limit`	No	返回最近事件数量，默认 50，最大 500。
`order`	No	事件排序，默认 desc 返回最新事件优先；asc 返回开盘后最早事件优先。	desc
`format`	No	content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
`sinceTime`	No	可选。仅返回该时间之后的事件，格式按上游事件 time 字段，例如 14:30:00。
`eventTypes`	No	可选。按上游事件 type 过滤，多个用英文逗号分隔。
`detailLevel`	No	档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。

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

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/ idempotentHint/ openWorldHint and non-destructive, covering the safety profile. The description adds genuine context: real-time event-stream semantics, second-level timestamps, and the required markdown-link format for stocks — behavior beyond the annotations, though it doesn't mention rate limits or staleness of the stream.

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-loads purpose, then usage, then output-format rules in clearly delimited segments. Efficient and structured, though the bracket markers make it slightly dense.

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 needn't be described, and the description still adds the essential cross-tool routing and link-formatting requirement. Complete enough for an agent to invoke correctly.

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 type/limit/order/format/sinceTime/eventTypes/detailLevel are all documented in the schema itself. The description adds little parameter-level meaning, so the baseline 3 is appropriate.

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: real-time push of limit-up sealing (封板) and breaking (炸板) events with second-level timestamps for intraday monitoring. It explicitly names the sibling it is not (limit_up_ladder), so an agent can distinguish them without opening schemas.

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?

Provides explicit '何时使用' guidance: use only when the user explicitly requests real-time events or latest sealing, otherwise use limit_up_ladder. The condition and the alternative are both spelled out, and the schema further routes limit-down queries to limit_down.

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.