Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

market_replay_workflow

Read-onlyIdempotent

一键生成 A 股市场复盘数据包：交易日判断、市场概况、涨跌停统计、涨停梯队、涨停主类排行、概念排行和每日简报；股票/资讯热榜默认不跑，可按需开启。 何时使用: 一键 A 股复盘：温度/宽度/涨跌停/梯队/题材/简报。默认 digest。问题问到题材为什么热时再开 includeHotlist。

Input Schema

NameRequiredDescriptionDefault
dateNo复盘交易日期，支持 YYYY-MM-DD 或 YYYYMMDD；不传默认今天，并会先调用 trading_calendar 辅助判断。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
returnModeNodigest=仅 stepDigest 摘要+nextActions（默认）；structured=各子步骤完整 data；rawSteps=完整 step 调试。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
includeHotlistNoAgent 自动判断。是否包含股票热榜和资讯热榜，默认 false。仅当问题关注多平台热度、新闻关注度、热门讨论或题材为什么热时开启。
includeBriefingNo是否包含每日简报，默认 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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds default behavior notes ('股票/资讯热榜默认不跑', '默认 digest'), but these largely restate defaults already documented in the input schema, so the added value beyond structured data is minimal.

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?

The description is front-loaded with the core purpose, followed by a compact usage section. The enumeration of components is necessary to convey scope, and the sentences are efficient, though the usage portion slightly repeats schema defaults with '默认 digest'.

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 the tool is a complex workflow with six optional parameters and a dedicated output schema, the description adequately covers purpose and usage context. It does not need to explain return values (output schema exists) nor safety (annotations cover it), but it could have mentioned the internal dependency on trading_calendar for date resolution (currently only in the schema) to better set expectations.

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 six parameters are fully documented in the schema itself. The description only reinforces the includeHotlist condition and default digest mode, which are already present in the schema parameter descriptions; it adds no new semantic detail beyond what the schema provides.

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 and resource: '一键生成 A 股市场复盘数据包' and enumerates the included components (trading day, market overview, limit up/down stats, ladder, theme rankings, briefing). This clearly distinguishes it as a composite workflow, though it does not explicitly name sibling workflows like limitup_review_workflow to further differentiate.

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?

Provides an explicit '何时使用' section with the primary use case ('一键 A 股复盘：温度/宽度/涨跌停/梯队/题材/简报') and a conditional instruction for enabling includeHotlist ('问题问到题材为什么热时再开 includeHotlist'). It lacks guidance on when not to use this tool or how it relates to alternative siblings, but the context 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