Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

short_term_emotion

Read-onlyIdempotent

查询早盘/盘中短线情绪快照，包含涨跌停、炸板率、晋级率、涨停委买额、一字封单额和市场宽度。用于快速判断短线情绪强弱。turnoverAmountYi 仅是情绪源附带成交额，不是交易所两市成交额；两市成交额请改用 index_market。 何时使用: 早盘/盘中短线情绪仪表盘：涨跌停、炸板率、晋级率、涨停委买额、一字封单、市场宽度。盘前数据未开始时返回 status=not_started 与 availableAfter，Agent 应按提示等待而不是循环重试。用户问"今天情绪怎么样/晋级率/封单/炸板率"时优先用它，再下钻 limit_stats/limit_up_ladder。turnoverAmountYi 不是交易所两市成交额；问两市/沪深成交额请改用 index_market。

Input Schema

NameRequiredDescriptionDefault
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
tradeDateNo交易日期，支持 YYYY-MM-DD 或 YYYYMMDD。不传默认最近交易日/今日盘中缓存。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description adds genuinely non-obvious behavior: pre-market returns status=not_started with availableAfter and the agent should wait rather than loop-retry, which is an operational trait annotations cannot express. It does not mention caching/pagination/refresh cadence, so it falls short of a 5.

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?

Front-loaded and well organized, but meaningfully redundant: the turnoverAmountYi/index_market caveat appears twice near-verbatim, and the '何时使用' block re-lists the same metric set already enumerated in sentence one. Trimming the duplicate caveat would lose no 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 an output schema present the description needn't explain return values, and it correctly focuses on routing, caveats, and the pre-market edge case. The only real gap is the duplicated caveat displacing room for other operational notes (e.g., data freshness or caching), leaving it slightly short of fully complete.

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 coverage is 100% with all three parameters (format, tradeDate, detailLevel) fully documented in the schema, so the baseline is 3. The description adds no syntax, default, or format guidance beyond the schema; the turnoverAmountYi caveat concerns an output field, not an input parameter.

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 verb+resource (query morning/intraday short-term sentiment snapshot) and enumerates the concrete metrics returned: limit up/down, broken-board rate, promotion rate, limit-up buy amount, one-word sealed orders, market breadth. It explicitly carves itself out from index_market for exchange turnover and names limit_stats/limit_up_ladder as drill-down siblings, 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 Guidelines5/5

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

Explicit '何时使用' block plus a routing rule for user phrasings ('今天情绪怎么样/晋级率/封单/炸板率' → use this first, then drill into limit_stats/limit_up_ladder). It also names the exclusion (turnoverAmountYi is not exchange turnover → use index_market) and specifies pre-market handling. Nothing about when to select this tool is left to inference.

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