Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

smart_hotlist

Read-onlyIdempotent

股票热榜：platform 默认 combined 综合热榜；也支持 ths=同花顺、eastmoney=东方财富、tgb=淘股吧、kaipanla=开盘啦等单平台热股排行，返回会保留平台信息。 何时使用: 股票热榜：多平台热股关注度排行；不可用作基本面证据或直接因果证据。 【链接】rows/items/嵌套股票对象含 code/name；列股必须用 [name(code)](https://stock.quicktiny.cn/quote/<code>) markdown 链接。

Input Schema

NameRequiredDescriptionDefault
typeNo兼容旧参数。可作为热榜范围别名；general/financial 会按 combined 处理。
limitNo返回数量，默认 30，最大 100。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
thsTypeNo单平台热榜周期，默认 hour。hour
listTypeNo榜单类型，默认 normal。normal
platformNo股票热榜平台，默认 combined 综合热榜；可选 ths=同花顺、eastmoney=东方财富、tgb=淘股吧、kaipanla=开盘啦。combined
stockTypeNo股票市场类型，默认 a。a
marketTypeNo市场范围，默认全部。
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.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 bar is lower. The description still adds real value: it states that platform information is preserved in the result and mandates a specific markdown link citation format for listed stocks, which is behavioral context not in the schema.

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 the resource and default behavior, followed by usage and citation rules. It is efficient given the amount of information, though the markdown-link rule is run together with the rest rather than set apart.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return structure need not be explained. The description covers platform selection, when-to-use, a negative-evidence caveat, and a required citation format, leaving nothing an agent needs in order to call the tool 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 the schema already documents all 9 parameters including enum values and defaults (limit, platform, format, stockType, marketType, detailLevel, etc.). The description largely restates the platform aliases already present in the schema and adds no syntax or format guidance beyond it, so the baseline of 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+resource: multi-platform stock attention hotlists (股票热榜), with the default (combined) and named single-platform variants. The scope is clear enough to separate it from stock_rank or news_hotlist, though it never explicitly names a sibling it could be confused with.

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 (multi-platform hot-stock attention rankings) plus a negative constraint that it must not be used as fundamental or causal evidence. This is strong when-to-use guidance, but it does not route the agent to a specific alternative tool.

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