Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

limit_up_ladder

Read-onlyIdempotent

实时按连板高度分层展示涨停股，清晰呈现当日连板梯队结构和晋级路径 何时使用: 涨停梯队、连板高度、龙头结构；返回 primaryThemeStats 表示按开盘啦主类聚合的涨停题材排行；配合 limit_stats、dragon_tiger。行内 firstLimitUpTime/lastLimitUpTime 是原始时间字段，给用户描述封板时间时优先读 firstLimitUpTimeText/lastLimitUpTimeText。 【链接】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

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add context — and it does: it names a return field (primaryThemeStats, aggregated by 开盘啦 main category), warns that firstLimitUpTime/lastLimitUpTime are raw timestamps with Text variants preferred for user-facing封板 times, and mandates markdown-link formatting. It does not discuss pagination or data latency, but this is solid added behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, then usage keywords, then return-field and link-format constraints — every clause is actionable for an agent. Dense but no filler sentences.

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 annotations carrying the safety profile, an output schema covering return values, and 100% param description coverage, the description's added output-field and formatting guidance makes the definition sufficient. Only minor gaps remain (no sibling-vs-sibling exclusion, no data freshness note).

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 already documented in the schema, and the description adds no parameter-level syntax or defaults beyond that. Baseline 3 applies when the schema does the heavy lifting.

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+scope: real-time display of limit-up stocks layered by consecutive-board height, exposing the ladder structure and promotion path. It names the concept unambiguously enough to distinguish it from siblings like limit_stats or dragon_tiger, which it explicitly references as companions.

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?

Includes an explicit '何时使用' clause (limit-up ladder, consecutive-board height, leader structure) and says to pair it with limit_stats and dragon_tiger. It gives clear context for selection but never states when NOT to use it or how it differs from e.g. limit_up_filter or broken_limit_up.

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