Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

limit_up_premium

Read-onlyIdempotent

统计涨停股次日溢价收益排行，量化打板策略的盈亏比和成功率 何时使用: 涨停次日溢价和历史胜率统计；不能单独作实时信号。 【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

NameRequiredDescriptionDefault
pageNo页码，默认 1。
limitNo每页数量，默认 20。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
sortByNo排序字段，默认 avgPremium。常用：avgPremium、winRate、limitUpCount。avgPremium
endDateYes必填。统计区间结束日期，支持 YYYY-MM-DD 或 YYYYMMDD。
sortOrderNo排序方向，默认 desc。desc
startDateYes必填。统计区间开始日期，支持 YYYY-MM-DD 或 YYYYMMDD。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
minLimitUpCountNo最少涨停样本数，默认 5。

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 declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds valuable non-obvious context: the 'not a real-time signal' caveat and the required markdown-link format for constituent stocks, which constrains how results must be rendered.

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-loads the core purpose in the first clause, then usage, then output-format constraint. Three compact segments with no filler, though the markdown-link instruction is dense and slightly detachable from the purpose statement.

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 covering safety and an output schema covering returns, the description only needs to add the non-obvious pieces, and it does: the non-real-time caveat and the mandatory link formatting for listed stocks. Minor gap in not clarifying result ordering semantics or date-range constraints.

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 every parameter (page, limit, format, sortBy, endDate, sortOrder, startDate, detailLevel, minLimitUpCount) is already documented in the schema. The description only hints at return structure (rows/items with code/name) rather than adding meaning to any parameter, so the baseline 3 applies.

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 and resource: statistics of next-day premium returns ranking for limit-up stocks, plus quantifying win rate/profit-loss ratio of the '打板' strategy. An agent can distinguish it from limit_up_ladder or limit_stats by the next-day premium focus, though no sibling is named explicitly.

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 gives 何时使用 (next-day premium and historical win-rate statistics) and a when-not condition (不能单独作实时信号 — cannot be used alone as a real-time signal). Clear context, but does not route to a named alternative for real-time needs.

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