Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

auction_theme_strength

Read-onlyIdempotent

默认按开盘啦题材聚合集合竞价表现，也可显式切到 CLS 概念或行业；输出竞价额、平均涨幅、高开数量、龙头候选和一致性；支持传 codes 只看自选股/观察池内部的主线强度。 何时使用: 题材集合竞价强度聚合：把全市场或自定义票池竞价数据按开盘啦题材/CLS 概念/行业聚合，默认开盘啦题材口径，回答"今天竞价资金打哪条主线"、"我的自选股里哪个方向最强"。未传日期且今天非交易日时按交易日历查询上一交易日并标注实际日期；显式日期不自动换日。

Input Schema

NameRequiredDescriptionDefault
codesNo可选。自定义票池（最多 100 只）。传入自选股/观察池后，仅在这些股票内部聚合题材强度；9:25 后可小票池冷算。
limitNo返回 top N 题材，默认 20，最大 50。
formatNocontent[0].text：standard/raw 默认 JSON 明细；summary 默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
tradeDateNo交易日期，支持 YYYY-MM-DD 或 YYYYMMDD。不传时：交易日取今日（9:25 前返回 AUCTION_DATA_NOT_READY）；非交易日按交易日历取上一交易日并标注实际日期。显式日期不自动换日。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
themeSourceNo题材分类口径，默认 kpl=开盘啦题材；可传 kpl/theme、cls/concept、industry。kpl
minBidAmountNo成员股入榜门槛（元），默认 500 万。
minMemberCountNo题材至少有几只成员入榜才纳入聚合，默认 3。

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：standard/raw 默认 JSON 明细；summary 默认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.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the non-trading-day fallback to the previous trading day with the actual date annotated, and that explicit dates are not auto-rolled. It does not cover rate limits or error conditions like AUCTION_DATA_NOT_READY (only the schema does).

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-loaded with the core behavior, then usage and date-edge handling in a logical order with no filler. It is dense and slightly repetitive (the aggregation scope is restated in the 何时使用 sentence), keeping it just under a 5.

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 an output schema present and annotations covering safety, the description does not need to explain returns and doesn't. It covers source selection, watchlist scoping, and the trading-calendar edge case, leaving only minor gaps like error-state messaging. Complete for an agent to call it correctly.

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 schema already documents every parameter, making 3 the baseline. The description reinforces key semantics (codes restricts aggregation to a watchlist, themeSource defaults to kpl, limit is top-N), but adds little that the schema does not already state, especially the minBidAmount/minMemberCount thresholds.

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?

It states a specific verb+resource: aggregating 集合竞价表现 by theme, with the default source (开盘啦题材) and switchable alternatives (CLS 概念/行业), plus the output fields (竞价额、平均涨幅、高开数量、龙头候选、一致性). This clearly separates it from market-wide siblings like auction_market_scan, though it stops short of naming those siblings explicitly.

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?

An explicit 何时使用 block gives concrete scenarios and even the questions it answers ("今天竞价资金打哪条主线"、"我的自选股里哪个方向最强"). It lacks explicit when-not or named-alternative routing against auction_data/auction_market_scan, so it lands at 4 rather than 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