Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

watchlist_update_stock

Idempotent

更新当前 API key 所属用户自选股条目的分组、标签、备注或来源上下文。写入工具，仅在用户明确要求移动股票分组、打标签或改备注时使用。 何时使用: 更新当前 API key 所属用户自选股条目的分组、标签、备注。groupMode=add 可把股票追加到新分组且保留原分组；replace 才是移动到新分组。适合用户说"把这些票移到某组/打标签/改备注"。 【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

NameRequiredDescriptionDefault
noteNo新的备注。
tagsNo要写入的标签数组。也兼容逗号分隔字符串。
codesNo兼容字段。逗号/空格分隔的股票代码或名称。
stockNo单只股票代码或名称。与 stocks/codes 任传其一。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
stocksNo批量股票代码或名称数组。最多 50 只。
groupModeNo分组写入模式。add=追加到该组且保留原分组；remove=从该组移除；replace=替换为该单一分组/清空。默认 replace。replace
groupNameNo要写入的分组名。传空字符串且 groupMode=replace 时可清空分组。每组最多 50 只股票。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
replaceTagsNotrue=用 tags 覆盖原标签；false=追加 tags。默认 true。
sourceContextNo新的来源上下文。

Output Schema

NameRequiredDescriptionDefault
dataNo
metaNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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。"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {},
+    "meta": {},
+    "success": {}
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the description's '写入工具' adds only confirmation. However, it adds real value by explaining groupMode=add preserves existing groups whereas replace moves (effectively replacing them), which is behavioral nuance 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose and usage, then adds helpful clarifications. It repeats '更新当前 API key 所属用户自选股条目的分组、标签、备注' twice, which is slight redundancy but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, when-to-use, behavioral nuances of group modes, and the important formatting constraint for linked stock references. With full schema coverage and the parameter constraint stated, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description goes further by clarifying the add vs replace semantics and the markdown link requirement for column stocks. Some parameters (format, detailLevel, replaceTags) aren't covered but are well documented in the schema.

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: updating group, tags, note, or source context of watchlist entries belonging to the current API key's user. This clearly distinguishes it from siblings like watchlist_add (adds entries) and watchlist_group_rename (renames a whole group).

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 conditions usage: '仅在用户明确要求移动股票分组、打标签或改备注时使用' and gives examples like '把这些票移到某组/打标签/改备注'. It does not name alternative sibling tools for adjacent operations, 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 toolsInspect
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.

Resources