Wudao A-Share Stock Data MCP

stock_rank

Read-onlyIdempotent

实时涨幅榜、跌幅榜、成交额榜、换手率榜等多维排行，盘中实时刷新何时使用: 全市场涨跌幅/成交金额/换手榜 + 盘中异动榜；参数用 type（或别名 rankType），支持 gainers/losers/amount 等，盘中异动用 speed_5m/speed_down_5m/amount_5m（5分钟涨速/跌速/成交额，分钟级更新）；changePercent/pctChange/涨幅榜会软映射到 gainers。返回 rows[] 附带前复权 change3d/change5d/change10d/change20d，普通多周期强弱比较不要重复调用多个 N 日榜；配合 theme_intraday_capital 找题材。【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

Name	Required	Description	Default
`type`	No	排行类型，默认 gainers。支持 gainers、losers、amount、turnover_rate、volume_ratio、intraday_drawdown、intraday_profit、overnight_drawdown、overnight_profit，也支持 gainers_Nd / losers_Nd；盘中异动榜：speed_5m=5分钟涨速、speed_down_5m=5分钟跌速、amount_5m=5分钟成交额（全市场分钟截面，metricValue 为窗口涨速%/成交额元，meta 带 momentumWindow）；volume 为旧兼容别名，实际等同 amount 成交金额榜；返回行会附带前复权 change3d/change5d/change10d/change20d。	gainers
`limit`	No	返回数量，默认 20，最大 200。
`format`	No	content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
`market`	No	市场范围，默认 all。常用：all、sh、sz、cyb、kcb。	all
`rankType`	No	type 的别名（agent 常误用 rankType）。与 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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: intraday refresh cadence for the speed_5m family, that minute-level metrics live in metricValue/meta, and the warning not to issue multiple N-day calls for period comparison.

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 body is one dense unpunctuated block that mixes usage, parameter aliases, return fields and link-formatting rules. It is informative yet hard to scan, and several clauses restate schema content already available elsewhere.

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?

An output schema exists, so return values need not be re-explained, yet the description still specifies the rows[]/code/name shape and the mandatory markdown link format, which is essential for correct output. Coverage is strong; only the lack of sibling disambiguation is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, setting the baseline at 3. The description still adds value the schema does not state, namely the soft-mapping of changePercent/pctChange/涨幅榜 onto gainers and the rankType alias behavior, which preempts a common invocation mistake.

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 states a specific verb and resource (实时涨幅榜、跌幅榜、成交额榜、换手率榜等多维排行) and enumerates the ranking dimensions and intraday refresh behavior. It is clearly distinguishable from siblings like stock_screener or limit_up_filter, and the return shape (rows[] with multi-period returns) is named.

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

Usage Guidelines4/5

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

It explicitly states 何时使用 (全市场涨跌幅/成交金额/换手榜 + 盘中异动榜) and names a companion tool (theme_intraday_capital) plus a do-not-repeat instruction for multi-period lists. However, it does not contrast against close siblings such as stock_screener or limit_up_filter, so routing boundaries are implied rather than enumerated.

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.