Wudao A-Share Stock Data MCP

cls_news

Read-onlyIdempotent

实时电报快讯原文，支持按关键词、股票、消息级别、时间范围过滤。用于盘前消息面复盘、盘中利好利空跟踪、个股相关消息查证。何时使用: 实时电报快讯：实时滚动的快讯原文，支持按关键词/股票/级别/时间过滤。短线盘前复盘、盘中消息面跟踪、个股利好利空查证的核心信息源。每条结果带 ref 字段（markdown 超链接格式），回答时直接将 ref 值嵌入正文作为可点击引用，不要另列 References 段落。

Input Schema

Name	Required	Description	Default
`date`	No	日期，YYYY-MM-DD 格式，默认今天。支持 today/yesterday。与 hoursAgo 互斥，hoursAgo 优先。
`level`	No	消息级别过滤。A=重大突发，B=重要，AB=A+B级，all=全部。默认 all。	all
`limit`	No	返回条数，默认 30，最大 100。
`format`	No	content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
`endTime`	No	时间范围终点 HH:mm，配合 date 使用。用户说"盘前消息"时填"09:25"。
`keyword`	No	内容关键词，支持逗号分隔多个。用户说"关于华为的消息"时填"华为"，说"芯片或半导体相关"时填"芯片,半导体"。
`hoursAgo`	No	最近N小时内的消息。优先级高于 date。用户说"最近2小时消息"时填 2。
`startTime`	No	时间范围起点 HH:mm，配合 date 使用。用户说"盘前消息"时填"06:00"。
`stockCode`	No	股票代码，匹配快讯关联股票字段。如 600519、000001。
`stockName`	No	股票名称，模糊匹配快讯内容和关联股票。如"贵州茅台"。
`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

A3.8/5.0

Behavior4/5

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

The annotations already carry the full safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description adds genuinely non-structured behavior: every result carries a 'ref' field in markdown-hyperlink form and the agent is told to inline it rather than emit a References section. That is a real output-handling convention not derivable from annotations or schema. It does not cover pagination or rate/limit behavior, keeping it at 4.

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?

The opening sentence ('实时电报快讯原文，支持按关键词、股票、消息级别、时间范围过滤') is repeated almost verbatim in the '何时使用' section, which wastes a large fraction of the text. The citation guidance is valuable and appropriately front-loaded, but the duplication prevents a higher score.

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?

For an 11-parameter read tool, the description plus a 100%-covered schema, existing output schema, and rich annotations leave little ambiguity: filters, usage scenarios, and the ref-citation output convention are all covered. The only gap is that it never clarifies its boundary against other news/disclosure siblings, so 4 rather than 5.

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 every one of the 11 parameters is already fully documented with examples (e.g. keyword='华为', hoursAgo semantics, date/hoursAgo precedence). The description only restates the filter categories at a high level and adds no parameter detail beyond the schema, which is the baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource ('实时电报快讯', real-time news flashes) with concrete filter dimensions (keyword/stock/level/time) and three concrete use scenarios. It is unambiguous what the tool returns and where it fits. It stops short of naming the adjacent siblings it must be distinguished from (news_hotlist, official_announcements), so it lands at 4 rather than 5.

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 maps the tool to real workflows: pre-market news review, intraday catalyst tracking, per-stock news verification. That is clear context for selection. However, it never states when NOT to use it or points to a preferred alternative (e.g. official_announcements for filings vs. this for rolling flashes), so no exclusions are given.

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.