Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

limit_down

Read-onlyIdempotent

实时获取当日跌停股池，含跌停原因、封单金额等，识别市场恐慌情绪 何时使用: 跌停池和负反馈分析。 【链接】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.6/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, openWorld, non-destructive), so the description's added value is real: it discloses real-time retrieval, the embedded data fields, and a mandatory output-format rule (stocks in lists must be rendered as markdown links `[name(code)](url)`). That formatting constraint is behavioral guidance not derivable from annotations or schema, though no rate limits or pagination behavior are described.

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

Conciseness3/5

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

Purpose is front-loaded, which is good, but the description crams purpose, usage, and an output-format mandate into dense run-on clauses, and the 【链接】 block sits awkwardly apart from the rest. It is compact but not cleanly structured.

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 need no explanation, and all parameters are schema-documented. The description supplies purpose, analytical use, and the markdown-link rendering rule, which is enough for a 6-param read-only tool. It could still note how it relates to adjacent limit-down tools to be fully complete.

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% and all six parameters (date, format, detailLevel, maxRowsPerLevel, includeFirstBoard, includeReasonInfo) are documented inline, so the schema carries parameter semantics fully. The description's mention of rows/items/nested code-name objects is output-structure guidance, not parameter meaning, so it adds nothing parameter-specific. Baseline 3.

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 concrete verb+resource: 实时获取当日跌停股池 (real-time retrieval of today's limit-down pool), plus the fields it carries (跌停原因、封单金额). This unambiguously distinguishes it from the many limit-up siblings since the resource is the down-side pool. It stops short of naming any sibling it should be chosen over, so not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The '何时使用' clause gives an analysis context (跌停池和负反馈分析 / negative-feedback analysis), which is better than nothing. But it is largely circular — telling the agent to use the limit-down tool for limit-down analysis — and gives no exclusions or named alternatives (e.g. broken_limit_up for 炸板). Implied usage only.

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