Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

broken_limit_up

Read-onlyIdempotent

实时获取当日曾触及涨停但未能封住的炸板股列表，含最高封单和开板次数 何时使用: 炸板池，判断市场分歧；配合 limit_stats。 【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

NameRequiredDescriptionDefault
dateYes必填。交易日期，支持 YYYY-MM-DD 或 YYYYMMDD。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
maxRowsPerLevelNo梯队/榜单每层最多返回行数。不传走档位默认（summary=3，standard=5）。
includeFirstBoardNo是否展开首板明细。不传=false（首板只统计数量）。
includeReasonInfoNo是否返回长文本涨停原因 reasonInfo。不传=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
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, idempotent, openWorld). The description adds real behavioral value: real-time sourcing, the returned fields, and a hard output-formatting requirement (列股必须用 [name(code)](...) markdown 链接) that the agent must honor. No pagination or rate-limit detail, but the output schema covers shape.

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?

Front-loaded with purpose, then usage, then the output/link requirement in three tight segments. Dense but every clause earns its place; the markdown-link rule is a necessary constraint rather than filler.

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 values needn't be re-explained, and the description still clarifies the rows/items/nested-stock shape plus the link mandate. Slight ambiguity remains between the 实时/当日 framing and the required date parameter, but overall it is complete enough to call correctly.

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 (date, format, detailLevel, maxRowsPerLevel, includeFirstBoard, includeReasonInfo) are already documented. The description adds no syntax or meaning beyond the schema, so this sits at the 3 baseline.

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+resource: 实时获取当日曾触及涨停但未能封住的炸板股列表, and names the fields it carries (最高封单、开板次数). This distinguishes it from sealed-limit siblings like limit_up_ladder, but it never distinguishes itself from the potentially overlapping board_break_analysis / limit_events.

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?

Explicitly states 何时使用: 炸板池，判断市场分歧, and routes the agent to combine it with limit_stats. Clear context is given, but there is no explicit when-not-to-use guidance or exclusion against the near-synonym siblings.

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