Wudao A-Share Stock Data MCP

official_disclosure_evidence

Read-onlyIdempotent

给定股票，聚合官方公告和官方互动问答，返回单股官方证据包。默认读站内记录；支持 keywords 多关键词证据包；verificationMode=auto 会先查站内记录，缺失时再补官网；verificationMode=live 较慢，仅用于明确要求。何时使用: 给单股同时返回公告和官方互动问答证据包。默认使用站内官方证据；支持 keywords 多关键词证据包；自动核验会先查站内记录，缺失时再补官网。【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

Name	Required	Description	Default
`code`	No	必填。股票代码或名称，例如 601991、大唐发电、601991.SH。与 stock/stockCode 任传其一。
`days`	No	相对回看天数，默认 30。传 startDate 时优先 startDate。
`limit`	No	每类证据返回数量，默认 10，最大 30。
`stock`	No	必填。股票代码或名称，例如 601991、大唐发电、601991.SH。与 stockCode/code 任传其一。
`format`	No	content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
`endDate`	No	证据结束日期，格式 YYYY-MM-DD；不传默认今天。
`keyword`	No	公告/问答关键词，例如算电协同、低空经济、重大合同。兼容单关键词调用；多关键词优先用 keywords。
`keywords`	No	多关键词证据包检索，数组或逗号/顿号分隔字符串，例如 ["算力","数据中心","火电"]。最多 10 个；返回记录会标注 matchedKeywords。
`maxPages`	No	实时核验或自动补查时最多检查页数，默认 2，最大 20。
`startDate`	No	证据开始日期，格式 YYYY-MM-DD；不传默认近 30 天。
`stockCode`	No	必填。股票代码或名称，例如 601991、大唐发电、601991.SH。与 stock/code 任传其一。
`detailLevel`	No	档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
`keywordMode`	No	多关键词匹配方式：any=命中任一关键词（默认）；all=同一条记录需命中全部关键词。	any
`interactionScope`	No	互动问答范围：all=深交所+上交所，szse=互动易，sse=上证 e 互动。	all
`verificationMode`	No	核验模式：default=站内记录（默认、最快）；live=官网实时核验（较慢，仅用户明确要求时使用）；auto=先查站内记录，无结果再实时核验。	default

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

Behavior4/5

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

With readOnlyHint/idempotentHint already covering the safety profile, the description adds real behavioral context: default reads station-internal records, auto backfills from the official site on misses, and live is slow and reserved for explicit requests. This is useful operational detail beyond the annotations.

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 description is noticeably redundant: the verificationMode auto/live behavior and the keywords support are stated both in the opening and again in the 何时使用 block, which largely repeats the purpose. The 【链接】 formatting note is valuable but the overall text wastes space on duplication.

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 and 100% schema coverage, the description needn't explain return values, and it does add the markdown-link formatting requirement plus mode behavior. It is essentially complete for calling the tool, with only minor redundancy.

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% and every one of the 15 parameters is already documented in the schema, so the description adds little parameter meaning. It restates the keywords and verificationMode semantics already present in the schema, warranting 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?

States a specific verb (聚合/aggregate) and resource (官方公告和官方互动问答) scoped to a single stock, and the aggregation aspect distinguishes it from the separate official_announcements and official_interactions siblings. An agent can tell what it returns without opening the schema.

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?

An explicit 何时使用 section plus mode guidance ('verificationMode=live 较慢，仅用于明确要求') tells the agent when to pick live vs default. It does not name the sibling tools (official_announcements/official_interactions) or say when to prefer them individually, so it falls short of full routing guidance.

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.