Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

macro_calendar

Read-onlyIdempotent

查询全球宏观财经日历，覆盖经济数据、央行/机构事件、国家/货币维度；适合回答未来几天有哪些重要经济数据或宏观事件。 何时使用: 宏观财经日历：查询未来/指定日期的全球经济数据和宏观事件，支持国家、货币、关键词过滤。适合"未来几天有哪些重要经济数据/央行事件"；不覆盖全部产业大会和产品发布。

Input Schema

NameRequiredDescriptionDefault
dateNo指定单日，支持 YYYY-MM-DD 或 YYYYMMDD。与 startDate/endDate 二选一。
limitNo返回数量，默认 50，最大 100。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
countryNo国家过滤，例如 中国、美国、欧元区、日本。
endDateNo区间结束日期，支持 YYYY-MM-DD 或 YYYYMMDD。不传默认未来 14 天。
keywordNo事件关键词模糊匹配，例如 非农、CPI、PMI、利率、GDP。
currencyNo货币过滤，例如 CNY、USD、EUR、JPY。
startDateNo区间开始日期，支持 YYYY-MM-DD 或 YYYYMMDD。不传默认今天。
detailLevelNo档位：默认 standard（Agent 可计算标准字段）；summary=压缩摘要；raw=全字段+原始数据。
minImportanceNo重要性下限，0-3。例如 2 表示只看较重要事件。

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
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only a scope boundary and nothing about defaults (e.g. the 14-day window, format/output behavior) beyond what the schema states; it is adequate but not rich.

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, but the description repeats itself: the opening sentence and the '何时使用' sentence restate the same coverage and use case with near-identical phrasing, and the same example ('未来几天有哪些重要经济数据') appears twice. Some redundancy costs efficiency.

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 not be described, and all ten params are fully documented at 100% coverage. Combined with annotations covering safety, the description supplies purpose, usage and scope boundaries, leaving little an agent needs missing.

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 one of the ten parameters is already fully documented with types, defaults and formats. The description reinforces country/currency/keyword filtering but adds no syntax or meaning beyond the schema. 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('查询全球宏观财经日历') and enumerates the covered domains (经济数据、央行/机构事件、国家/货币维度). It bounds scope by noting it does not cover industry conferences and product launches, which helps distinguish it from calendar siblings, though it never names an alternative tool.

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?

Contains an explicit '何时使用' section and a concrete example use case ('未来几天有哪些重要经济数据/央行事件'), plus a negative exclusion ('不覆盖全部产业大会和产品发布'). This is strong when-to-use guidance, but it stops short of naming sibling tools like market_catalyst_calendar or stock_event_calendar as the alternative to prefer.

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