Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

watchlist_remove

DestructiveIdempotent

从当前 API key 所属用户的私有自选股中移除用户明确指定的股票。写入工具，仅在用户明确要求删除/移除时使用。 何时使用: 从当前 API key 所属用户的自选股中移除股票。只有用户明确要求移除/删除自选时调用。 【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

NameRequiredDescriptionDefault
codesNo兼容字段。逗号/空格分隔的股票代码或名称。
stockNo单只股票代码或名称。与 stocks/codes 任传其一。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
stocksNo批量股票代码或名称数组。最多 50 只。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。

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/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, so the safety profile is covered. The description adds real value beyond those: the operation is scoped to the current API key user's own private watchlist, and it must only run on an explicit user request. It stops short of stating reversibility or permission requirements.

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 core constraint is front-loaded, but the requirement to call only on explicit user request is restated verbatim across two sentences ('仅在用户明确要求删除/移除时使用' and '只有用户明确要求移除/删除自选时调用'), which is redundant rather than reinforcing. Reasonable length, but not zero-waste.

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?

An output schema exists, so return values need not be explained. Given a destructive, idempotent write tool with full annotation coverage, the description supplies purpose, usage gating, and output-formatting convention; the omission of permission/authentication prerequisites is a minor residual gap.

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 stock/stocks/codes/format/detailLevel are already documented in the schema. The description's link-formatting rule adds some guidance about how stocks should be rendered but does not clarify the one-of constraint among stock/stocks/codes beyond what the schema description already states. Baseline 3 applies.

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: remove explicitly specified stocks from the current API key user's private watchlist. This clearly separates it from watchlist_add and watchlist_update_stock. The write-tool framing is front-loaded and unambiguous.

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?

Explicit when-to-use ('何时使用: 从当前 API key 所属用户的自选股中移除股票') and when-not ('只有用户明确要求移除/删除自选时调用'), which is exactly the guardrail an agent needs for a destructive tool. It does not name a specific alternative sibling, so it falls short of a full 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