Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

limitup_review_workflow

Read-onlyIdempotent

一键生成涨停板复盘数据包：涨跌停统计、涨停梯队、涨停主类排行、炸板池、跌停池，可选涨停溢价统计。 何时使用: 一键涨停复盘：涨跌停统计/梯队/题材/炸板/跌停。默认 digest。盘中事件分析问题再开 includeEventSummary。

Input Schema

NameRequiredDescriptionDefault
dateNo复盘交易日期，支持 YYYY-MM-DD 或 YYYYMMDD；不传默认今天。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
endDateNo涨停溢价统计结束日期，includePremium=true 时使用。
startDateNo涨停溢价统计开始日期，includePremium=true 时使用。
returnModeNodigest=仅 stepDigest 摘要+nextActions（默认）；structured=各子步骤完整 data；rawSteps=完整 step 调试。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
includeBrokenNo是否包含炸板池和跌停池，默认 true。
includePremiumNo是否在 startDate/endDate 存在时包含涨停溢价统计，默认 false。
includeEventSummaryNoAgent 自动判断。是否额外分析封板/炸板事件流，默认 false。仅当问题关注盘中封板过程、情绪拐点、炸板潮、尾盘事件、反复开板回封或实时监控时开启。普通涨停复盘不需要。

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.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and idempotency profile is fully covered. The description adds useful context that this is a multi-step composite workflow and that the default return mode is digest, but that default is also already stated in the schema, so added behavioral value is modest.

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?

Two sentences, front-loaded with the package contents before the usage guidance, so an agent gets the 'what' first. There is mild redundancy between the opening content list and the 何时使用 list of the same items, but it is compact and wastes little space.

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?

Given a workflow tool with 9 optional parameters, no required params, and a rich schema plus an existing output schema, the description covers what the package contains, when to use it, and the key conditional flags, so return values need not be explained here. It is complete enough to invoke correctly, with only the sibling-alternative routing left implicit.

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% with all 9 parameters documented, so the schema carries the semantic load; the baseline is 3. The description restates includePremium and includeEventSummary conditions, which map to those params but do not add meaning beyond the schema text.

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?

The description uses a specific verb (一键生成) with a clearly scoped resource (涨停板复盘数据包) and enumerates exactly what the package aggregates: 涨跌停统计、涨停梯队、涨停主类排行、炸板池、跌停池. This lets an agent distinguish it as a composite one-shot review tool from single-purpose siblings such as limit_stats, limit_up_ladder, limit_up_premium, broken_limit_up, and limit_down.

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?

A dedicated '何时使用' clause states the scenario (一键涨停复盘 across 统计/梯队/题材/炸板/跌停), and it adds a conditional rule for opening includeEventSummary during 盘中事件分析 while noting 普通涨停复盘不需要. It does not, however, explicitly name single-purpose siblings as the alternative when only one slice is needed.

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