Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

theme_stocks

Read-onlyIdempotent

题材成分股主入口。传入 theme_intraday_capital 的 themeCode（如 801843k）或题材名；返回成分股代码、名称、热度与标签。 何时使用: 题材成分股主入口：传 theme_intraday_capital 的 themeCode（如 801843k）或题材名。不要用已隐藏的 concept_stocks。 【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

NameRequiredDescriptionDefault
kplIdNo开盘啦题材库数字 ID（可选）。
limitNo返回成分股数量，默认 50，最大 300。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
themeCodeNo开盘啦盘中板块代码，来自 theme_intraday_capital.rows[].themeCode，例如 801843k。
themeNameNo开盘啦题材名称，例如 商业航天 / 低空经济。可与 themeCode 二选一；同时传时以能解析到的题材名为准。
tradeDateNo可选。当只用 themeCode 时，用于从当日 theme_intraday_capital 快照反查题材名，格式 YYYYMMDD。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
onlyLimitUpNo仅返回题材库标记为涨停的成分股，默认 false。
syncIfMissingNo本地题材库未命中时，是否调用开盘啦 Theme API 搜索并同步，默认 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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds the return contents and a mandatory markdown-link formatting rule for listed stocks, which is useful output-side context, but says nothing further about pagination, rate limits, or the effect of syncIfMissing.

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 purpose statement and the 何时使用 block are near-duplicates of each other, repeating '题材成分股主入口' and the 801843k example verbatim. The linking rule is front-loadable but the middle of the text is redundant padding rather than new information.

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 nine optional parameters, an output schema, and full schema coverage, the description supplies what is missing: the entry-point framing, the sibling to source themeCode from, the exclusion, and the output link format. Only edge cases like sync behavior and result size are left wholly to the schema.

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 all nine parameters are already documented, including the themeCode/themeName relationship and tradeDate fallback. The description only repeats the themeCode example and adds no syntax or precedence detail beyond the schema, so the 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 resource (题材成分股) and enumerates the return fields (code, name, heat, tags), and positions itself as the '主入口'. It also names the source sibling (theme_intraday_capital) and explicitly excludes the hidden concept_stocks, so an agent can distinguish it without opening any schema.

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 何时使用 block gives a concrete trigger condition (pass a themeCode from theme_intraday_capital or a theme name) and one explicit negative (不要用已隐藏的 concept_stocks). It lacks guidance on choosing between themeCode vs themeName beyond 'pick one', but the core routing is clear.

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