Wudao A-Share Stock Data MCP

index_market

Read-onlyIdempotent

查询指数搜索、实时快照、涨幅/成交额排行、日线和分钟线。实时快照、排行和当日分钟线读取站内持续落盘数据，不会因单次调用现场冷取；用于三大指数、宽基指数、行业指数点位和走势分析。两市成交额及量能变化直接读取 summary.marketTurnover 或 marketTurnoverSeries；市场宽度仍使用 market_overview。何时使用: 指数行情工具：查三大指数/宽基/行业指数点位、涨跌幅、成交额排行、日线和分钟线。用户问"两市成交额/沪深成交额/全市场成交额/量能变化"时用 summary.marketTurnover 或 marketTurnoverSeries；不要自行混加不同 amountScope 的指数行，也不要用 market_overview 或 short_term_emotion 代替。

Input Schema

Name	Required	Description	Default
`code`	No	可选。单个指数代码；等价于 symbols 单元素。
`mode`	No	查询模式，默认 snapshot。search=搜索指数；snapshot=实时快照；rank=排行；daily=日线；minute=分钟线。	snapshot
`limit`	No	返回数量，snapshot 默认 30，rank 默认 50；日线/分钟默认返回尾部窗口。
`order`	No	排序方向，默认 desc。	desc
`format`	No	content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
`period`	No	minute 模式周期，默认 1m。	1m
`sortBy`	No	rank/snapshot 排序字段，默认 pctChg；可选 pctChg/amount/close/vol。	pctChg
`endDate`	No	可选。daily 模式结束日期，支持 YYYY-MM-DD 或 YYYYMMDD。
`keyword`	No	可选。名称/代码/分类关键词。search 模式按关键词搜索；snapshot/rank 模式用于过滤。
`symbols`	No	可选。指数代码，数组或逗号分隔字符串。daily/minute 模式建议显式传入。
`startDate`	No	可选。daily 模式起始日期，支持 YYYY-MM-DD 或 YYYYMMDD。
`tradeDate`	No	可选。交易日期，支持 YYYY-MM-DD 或 YYYYMMDD；daily/minute 模式可指定日期。
`detailLevel`	No	档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
`forceRefresh`	No	调试用。true 时绕过共享结果缓存；指数实时模式仍只读取最新落盘快照，不会由用户请求触发现场刷新。

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

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered; the description adds real behavioral context beyond that — real-time snapshot, rank and intraday minute modes read continuously persisted site data and will not cold-fetch on a single call, and forceRefresh bypasses cache but still cannot trigger a live refresh. It stops short of documenting rate limits or latency expectations.

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?

The purpose and mode list are front-loaded and the description is organized into a scope statement followed by a 何时使用 block. However, the turnover guidance ('两市成交额及量能变化… marketTurnoverSeries') is stated twice, which is wasted space in an already dense paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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; the description instead covers the things structure cannot — data freshness semantics, mode selection, sibling routing, and the amountScope caveat. For a zero-required-param, 14-parameter tool this is complete enough to invoke correctly.

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 description coverage is 100% with all 14 params documented, so the schema carries the baseline. The description still adds value by scoping which mode each input belongs to (daily/minute 建议显式传入 symbols, snapshot/rank keyword as filter) and by warning against mixing rows of differing amountScope, which is a semantic constraint not expressed in the schema.

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+resource (查询指数：搜索、实时快照、排行、日线、分钟线) and enumerates the five modes mirroring the schema enum, so an agent knows exactly what surface it covers. It also explicitly distinguishes itself from siblings index-adjacent tools by naming market_overview and short_term_emotion as the wrong choices for breadth/emotion questions.

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?

It contains a dedicated 何时使用 section giving the trigger conditions (三大指数/宽基/行业指数点位、涨跌幅、成交额排行、日线分钟线) and the exclusions ('不要用 market_overview 或 short_term_emotion 代替', '不要自行混加不同 amountScope 的指数行'). It also routes two-market turnover questions to summary.marketTurnover / marketTurnoverSeries, which is an actionable alternative.

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.