Wudao A-Share Stock Data MCP

official_announcements

Read-onlyIdempotent

查询上市公司正式公告。默认读取站内记录；支持 keywords 多关键词一次检索并返回 matchedKeywords；verificationMode=live 较慢，仅用于用户明确要求官网实时核验；verificationMode=auto 会先查站内记录，缺失时再补查官网。何时使用: 查上市公司正式公告。默认使用站内记录；支持 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/keywordStock 任传其一。
`days`	No	相对回看天数，默认 30。传 startDate 时优先 startDate。
`page`	No	页码，默认 1。
`limit`	No	返回数量，默认 20，最大 100。
`stock`	No	股票代码或名称，例如 601991、大唐发电、601991.SH。与 stockCode/code/keywordStock 任传其一。
`format`	No	content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
`endDate`	No	公告结束日期，格式 YYYY-MM-DD；不传默认今天。
`keyword`	No	公告标题/正文关键词。兼容单关键词调用；多关键词优先用 keywords。
`category`	No	官方实时查询类型别名，通常不必传。
`keywords`	No	多关键词并行检索，数组或逗号/顿号分隔字符串，例如 ["算力","数据中心","火电"]。最多 10 个；返回 rows 会标注 matchedKeywords。
`maxPages`	No	实时核验或自动补查时最多检查页数，默认 1，最大 20。
`startDate`	No	公告开始日期，格式 YYYY-MM-DD；不传默认近 30 天。
`stockCode`	No	股票代码或名称，例如 601991、大唐发电、601991.SH。与 stock/code/keywordStock 任传其一。
`stockName`	No	公司简称关键词。
`pageColumn`	No	巨潮栏目/市场筛选，通常不必传。
`detailLevel`	No	档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
`keywordMode`	No	多关键词匹配方式：any=命中任一关键词（默认）；all=同一条记录需命中全部关键词。	any
`keywordStock`	No	股票代码或名称别名。
`announcementType`	No	公告类型筛选，通常不必传。
`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.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, so the safety profile is covered. The description adds real operational context beyond that: live mode is slower, auto mode falls back, rows carry matchedKeywords, and — importantly — an output formatting requirement (markdown link for stock codes) that the agent must follow.

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?

Front-loaded and readable, but the default/site-record vs live/auto behavior is stated twice — once in the opening paragraph and again under 何时使用 — which is genuine redundancy for an otherwise tight description.

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 20 parameters, no required fields, an output schema, and full annotation coverage, the description supplies the decision-relevant extras an agent needs: mode selection rules, multi-keyword behavior, and a mandated output link format. Only the duplicate mode explanation and lack of return-shape hints (mitigated by the output schema) keep it short of perfect.

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 20 parameters, including verificationMode, keywords, and the stock aliases. The description largely restates the same mode semantics rather than adding syntax or format detail beyond the schema, so baseline 3 applies; the link-format note is output guidance, not a parameter clarification.

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 (查询上市公司正式公告) and a clear scope: official announcements for listed companies, with date/keyword/stock filtering. An agent can distinguish it from news-oriented or filing-oriented siblings even though no sibling is named explicitly.

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?

Gives explicit when-to-use guidance and names the alternative modes with their selection conditions: default site records, live only when the user explicitly requests official-site verification, auto only for fallback when site records are missing. Nothing about mode choice is left 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.