Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

watchlist_list

Read-onlyIdempotent

读取当前 API key 所属用户的私有自选股列表，返回分组、标签、备注和最近涨停上下文。只读工具。 何时使用: 读取当前 API key 所属用户的自选股列表，可按 groupName 筛选，并返回分组、标签、备注和最近涨停上下文。只在用户明确问"我的自选/自选股列表/观察池"时使用。 【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

NameRequiredDescriptionDefault
limitNo返回数量，默认 200，最大 500。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
groupNameNo可选。只查看某个自选分组。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
includeLimitUpContextNo是否带最近涨停/连板上下文，默认 true。

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 cover readOnly/idempotent/non-destructive/openWorld, so the safety profile is free. The description adds genuinely useful behavior beyond that: rows/items contain nested stock objects with code/name, and listing rows must be rendered as `[name(code)](https://stock.quicktiny.cn/quote/<code>)` markdown links – a formatting obligation not present in annotations or schema.

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 first sentence and the follow-up usage sentence repeat nearly identical content ("读取当前 API key 所属用户的自选股列表...返回分组、标签、备注和最近涨停上下文"), which is wasted space. Front-loading is decent and the link rule is clearly marked, but the redundancy costs it.

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 a full output schema, complete parameter coverage and rich annotations, the description only needs to add the rendering/formatting contract, which it does. Nothing critical is missing for correct invocation.

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 the baseline is 3. The description only restates groupName filtering and the returned fields, adding no syntax or format detail beyond what the schema already documents for limit, format, detailLevel and the others.

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?

States a specific verb+resource+scope: reading the current API key owner's private watchlist, returning groups, tags, notes and recent limit-up context. Read-only framing helps separate it from watchlist_add/remove/update siblings, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Contains an explicit 何时使用 section plus a tight trigger condition ("只在用户明确问'我的自选/自选股列表/观察池'时使用"), so the agent knows both when to call it and when not to. This is more than most sibling tools offer.

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