Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

auction_data

Read-onlyIdempotent

集合竞价阶段逐笔数据，含历史分位、量比、涨停委买额和 20 分后涨停委买额，开盘前发现异动信号 何时使用: 单股/多股集合竞价明细（必须传 code/codes）。全市场排行→auction_market_scan；题材聚合→auction_theme_strength；昨涨停/昨炸板今表现→auction_opening_snapshot。

Input Schema

NameRequiredDescriptionDefault
codeNo单只股票代码或名称，例如 600519、600519.SH、贵州茅台。返回包含 limitBuyAmount/limitBuyAmountAfter920 等涨停委买字段（若当日命中）。
codesNo多只股票代码或名称，逗号分隔，例如 600519,300750,宁德时代。
limitNo返回数量，默认 20，最大 60。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
end_dateNo区间结束日期，格式 YYYYMMDD。
start_dateNo区间开始日期，格式 YYYYMMDD。
trade_dateNo交易日期，格式 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.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description is not burdened with that. It adds value by disclosing the content of the payload and by stating a required-input constraint that annotations do not carry. It stops short of behavior like rate limits or pagination, keeping it at a 4.

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?

Content summary is front-loaded before the usage/routing guidance, and the routing arrows are compact. It is slightly dense with multiple field names packed into the first clause, but no sentence is wasted.

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?

An output schema exists, so return-format explanation is unnecessary. Between the annotations, full schema coverage, and the routing guidance, an agent has enough to invoke correctly; only minor behavioral detail is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema documents each parameter, giving a baseline of 3. The description adds meaning beyond the schema by asserting that code/codes is mandatory for this tool even though the schema lists zero required parameters, clarifying the key parameter relationship.

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 and resource (集合竞价阶段逐笔数据) and enumerates the returned fields (历史分位、量比、涨停委买额、20分后涨停委买额). It explicitly differentiates itself from sibling tools by naming specific alternatives and their scope, so an agent can route 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?

Provides an explicit '何时使用' block with the trigger condition (单股/多股集合竞价明细) plus a hard constraint (必须传 code/codes). It also routes three distinct use cases to their correct alternatives: auction_market_scan, auction_theme_strength, and auction_opening_snapshot.

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