Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

news_hotlist

Read-onlyIdempotent

聚合全网热点与财经媒体热榜，观察资讯关注度和潜在题材线索。 何时使用: 资讯热榜：全网/财经媒体热点话题排行；用于观察消息面温度和潜在题材线索。

Input Schema

NameRequiredDescriptionDefault
limitNo返回数量，默认 30，最大 100。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
categoryNo资讯类别，默认 financial。general=全网热点，financial=财经资讯，all=全部。单平台榜单时可不传。financial
platformNo资讯热榜平台，默认 combined 综合热榜；可选 douyin=抖音、weibo=微博、baidu=百度、toutiao=今日头条、eastmoney=东方财富、ths=同花顺、sina=新浪财经、yicai=第一财经。combined
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only that data is aggregated across全网 and financial media sources - useful scope context but no freshness, source coverage, or rate-limit detail, so it clears the (lower) annotated bar without being rich.

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?

Two short clauses, front-loaded with the resource and scope, then the usage note. Slightly redundant - '观察资讯关注度和潜在题材线索' is restated as '观察消息面温度和潜在题材线索' - but there is no padding or boilerplate.

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 five fully documented optional parameters, a rich enum set, an output schema, and annotations covering the safety profile, the description supplies enough to call the tool correctly without restating return values. The one real gap - no differentiation from the many sibling news/hotlist tools - is a routing issue rather than a completeness one.

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%, with limit, format, category, platform and detailLevel all documented in the schema, including enum meanings and defaults. The description adds nothing about parameter behavior, so the baseline 3 applies - the schema carries the entire parameter burden.

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?

The description states a concrete verb+resource: aggregating all-network hot topics and financial-media rankings, with the goal of watching news sentiment and potential theme leads. That is clear enough to identify the tool. However, it never distinguishes itself from close siblings such as smart_hotlist, cls_news, or briefings, leaving the agent to guess which hotlist/news tool applies.

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?

There is an explicit '何时使用' section naming the scenario (all-network / financial media hot-topic rankings, gauging news temperature). That is more than implied usage, but it offers no when-not-to-use conditions and names no alternative tool, so routing between news_hotlist, cls_news and smart_hotlist is left entirely to inference.

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