Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

market_catalyst_calendar

Read-onlyIdempotent

查询政策会议、行业大会、产品发布、指数调整、经济数据和假日等未来催化事件。适合回答"未来几天有什么短线催化/大会/发布会/政策生效"。 何时使用: 短线催化日历：查询政策会议、行业大会、产品发布、指数调整、重要经济数据和假日等未来催化事件。用户问"未来几天有什么短线催化/大会/发布会/政策生效/行业会议"时优先使用；不是上市公司公告原文。

Input Schema

NameRequiredDescriptionDefault
dateNo指定单日，支持 YYYY-MM-DD 或 YYYYMMDD。与 startDate/endDate 二选一。
typeNo事件类型：all/0=全部；economic/1=经济数据；event/2=事件/产业催化；holiday/3=假日。默认 all。
limitNo返回数量，默认 50，最大 120。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
countryNo国家/地区过滤，例如 中国、美国、日本、中国台湾。
endDateNo区间结束日期，支持 YYYY-MM-DD 或 YYYYMMDD。不传默认未来 14 天。
keywordNo标题关键词过滤，例如 发布会、大会、论坛、指数、华为、机器人。
minStarNo快讯星级下限，通常 1-5；例如 5 只看高星事件。
startDateNo区间开始日期，支持 YYYY-MM-DD 或 YYYYMMDD。不传默认今天。
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 and idempotency profile is covered without description help. The description adds the scope exclusion (not announcement full text) but says nothing about pagination, date-default behavior, or rate limits beyond what the schema states. With annotations carrying most of the load, a 3 is appropriate.

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

Conciseness2/5

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

The text is redundant: the opening sentence listing catalyst categories is repeated almost verbatim inside the '何时使用' section, and the sample user query appears twice. Nothing is wrong in content, but roughly half the length is duplicated rather than front-loaded with new information.

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?

For a 10-parameter read-only tool with an output schema, full schema coverage, and rich annotations, the definition covers purpose and trigger conditions adequately. The remaining gap is sibling disambiguation against macro_calendar/stock_event_calendar, which matters given how many calendar tools exist. Otherwise an agent can call this 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 every parameter (date/startDate/endDate ranges, type enum, limit, format, country, keyword, minStar, detailLevel) is already documented in the schema. The description adds no syntax, format, or defaulting detail beyond it. Baseline 3 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?

The description names a specific verb+resource: querying future catalyst events across policy meetings, industry conferences, product launches, index adjustments, economic data, and holidays. It also draws one explicit boundary (not company announcement original text), which separates it from official_announcements. However, it never distinguishes itself from the close siblings macro_calendar or stock_event_calendar, which cover overlapping calendar semantics.

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?

It gives a clear usage condition: use when the user asks what short-term catalysts/conferences/launches/policy effective dates fall in the coming days, and it explicitly excludes announcements. That is real routing guidance, but no alternative tool is named for the boundary cases (e.g., macro_calendar for pure macro data, stock_event_calendar for per-stock events), so the agent must still guess on adjacency.

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