Skip to main content
Glama

Wudao A-Share Stock Data MCP

auction_data

Read-onlyIdempotent

集合竞价阶段逐笔数据,含历史分位、量比、涨停委买额和 20 分后涨停委买额,开盘前发现异动信号 何时使用: 单股/多股集合竞价明细(必须传 code/codes),只返回 9:25 定盘结果;要单股 9:15/9:20 时点的价格、涨幅或涨停买单,用 auction_market_scan 传 codes=[代码]、snapshotTime、tradeDate,并设 minBidAmount=0。全市场排行→auction_market_scan;题材聚合→auction_theme_strength;昨涨停/昨炸板今表现→auction_opening_snapshot。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "auction_data"
  }
}

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 already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds important behavior beyond annotations: it only returns the 9:25 final result and requires code/codes, though it does not describe error behavior or date-range edge cases.

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 purpose is front-loaded, followed by a compact 何时使用 routing block. It is dense and every clause is useful, though slightly long due to multiple sibling-tool exclusions.

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 and fully described parameters, the definition gives enough information to select and invoke the tool correctly, including the 9:25-only constraint and sibling routing. A minor gap is that it does not clarify behavior if both code and codes are supplied, or default date/range behavior.

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 all 8 parameters are already well documented. The description adds meaningful context not captured by the schema's empty required list: it states that code/codes must be passed and distinguishes single-stock versus multi-stock usage.

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 resource (集合竞价 data) and the fields it contains (历史分位、量比、涨停委买额、20 分后涨停委买额), plus the pre-open anomaly-discovery use case. It explicitly distinguishes itself from auction_market_scan, auction_theme_strength, and auction_opening_snapshot.

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?

Has an explicit 何时使用 section: must pass code/codes, only returns 9:25 final result, and directs 9:15/9:20 snapshot requests to auction_market_scan with snapshotTime, tradeDate, and minBidAmount=0. It also routes whole-market ranking, theme aggregation, and prior-day limit-up performance to named sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.