Wudao A-Share Stock Data MCP

watchlist_add

Idempotent

把用户明确指定的股票加入当前 API key 所属用户的私有自选股，支持批量、去重、自动分组、标签和备注。写入工具，仅在用户明确要求加入自选时使用。何时使用: 把用户明确指定的一只或多只股票加入当前 API key 所属用户的自选股。自选总数最多 300 只，每组最多 50 只；同一股票可属于多个组。支持股票名称/代码混输、批量去重、自动分组（连板/首板/题材/行业）和备注标签。只有用户明确要求"加入自选/加到观察池/帮我收藏这些票"时调用。【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

Name	Required	Description	Default
`note`	No	可选备注。
`tags`	No	可选标签数组，例如 ["机器人","连板观察"]。也兼容逗号分隔字符串。
`codes`	No	兼容字段。逗号/空格分隔的股票代码或名称，例如 "中际旭创,300750,600839"。
`stock`	No	单只股票代码或名称，例如 600519、贵州茅台。与 stocks/codes 任传其一。
`format`	No	content[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
`stocks`	No	批量股票代码或名称数组，例如 ["中际旭创","300750","600839"]。单次最多 50 只；自选总数最多 300 只。
`position`	No	加入位置。top=放到自选股最前；bottom=放到末尾。默认 top。	top
`groupName`	No	手动分组名。传入后默认使用该分组。每组最多 50 只股票；同一股票可属于多个组。
`detailLevel`	No	档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
`groupStrategy`	No	分组策略。auto=按连板/首板/题材/行业自动分组；manual=使用 groupName；none=不分组。默认：有 groupName 时 manual，否则 auto。
`sourceContext`	No	可选来源上下文，例如"盘后复盘看到承接不错"。

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?

Annotations already declare the write/safe/idempotent profile, and the description correctly reinforces the write nature. It adds real behavioral context beyond annotations: hard caps (300 total, 50 per group), that a stock may belong to multiple groups, dedup behavior, and auto-grouping strategies (连板/首板/题材/行业).

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 text is repetitive: the batching/dedup/auto-group/tag support and the watchlist-scope are restated in both the opening and the '何时使用' block. The link-formatting sentence adds value but is buried at the end.

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 a write tool with an output schema present, the description need not explain return values, and it covers the key constraints an agent needs (at-least-one input field via schema, caps, grouping strategy defaults). It could still clarify how auto-grouping interacts with groupName overrides, but overall it is complete enough.

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 coverage is 100%, so the schema already documents all 11 parameters including the at-least-one-of constraint and enum meanings. The description only loosely reinforces batch/tags/notes/grouping already covered by schema descriptions. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (加入/add) and resource (私有自选股) with precise scope: the private watchlist of the user owning the current API key. It also flags that this is a write tool (写入工具), distinguishing it from read siblings like watchlist_list and mutation siblings like watchlist_remove/watchlist_update_stock.

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?

Explicitly cues invocation with a dedicated '何时使用' section and example trigger phrases ('加入自选/加到观察池/帮我收藏这些票'), plus a constraint that it should only be called on explicit user request. It stops short of naming alternative tools (e.g. watchlist_update_stock) that should be used instead when the goal is modifying an existing entry.

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.