Wudao A-Share Stock Data MCP

research_reports

Read-onlyIdempotent

券商研报查询：个股评级、目标价、盈利预测，支持按股票或关键词搜索何时使用: 券商研报和评级；配合 kline、capital_flow。【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

Name	Required	Description	Default
`page`	No	页码，默认 1。
`format`	No	content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
`sortBy`	No	排序字段，默认 publishDate。	publishDate
`endDate`	No	研报结束日期，格式 YYYY-MM-DD。
`keyword`	No	关键词，例如人工智能、算力、公司简称。
`pageSize`	No	每页数量，默认 10。
`sortOrder`	No	排序方向，默认 desc。	desc
`startDate`	No	研报开始日期，格式 YYYY-MM-DD。
`stockCode`	No	股票代码或名称。可与 keyword 搭配。
`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.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/open-world/non-destructive, so the safety profile is covered. The description adds genuinely non-annotated context: the output-link convention that stock mentions must be rendered as markdown links using code/name—a real behavioral requirement for the agent. Pagination/rate-limit behavior is left unstated, preventing a 5.

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?

Purpose is front-loaded, then usage, then formatting convention—a logical order. It is dense but every clause carries information; the link-formatting block is somewhat verbose but functional rather than filler.

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, the description need not explain return values, and it rightly focuses on purpose, usage, and link formatting. For a 10-parameter but well-documented query tool this is complete, though it could note pagination/format interactions slightly more.

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 parameter (page, format, sortBy, dates, keyword, stockCode, detailLevel, etc.) is already documented in the schema. The description's mention of stock/keyword search adds little beyond what the schema states, so the baseline 3 is appropriate.

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 enumerates the concrete content it returns (个股评级、目标价、盈利预测) plus its two search modes (按股票或关键词). An agent can distinguish it from siblings like stock_research_workflow or sector_analysis at a glance.

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?

The '何时使用' clause gives clear context (broker research reports and ratings) and explicitly names complementary siblings (kline, capital_flow). It stops short of stating when NOT to use it or naming a disambiguating alternative, so it falls short of a 5.

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.