Skip to main content
Glama

Wudao A-Share Stock Data MCP

by io.github.jcdreamjc
OverviewDiscussionsAdmin

stock_event_calendar

Read-onlyIdempotent

聚合限售解禁、股东增减持、回购、分红除权和财报披露计划，用于短线排雷、事件驱动和盘前风险检查；不是宏观财经日历/产业大会日历。eventTypes 支持 unlock/holder_trade/repurchase/dividend/disclosure。 何时使用: 公司事件/风险日历：聚合限售解禁、股东增减持、回购、分红除权、财报披露计划。短线用途是排雷、解释事件驱动和盘前风险检查；不是宏观财经日历/产业大会日历。

Input Schema

NameRequiredDescriptionDefault
codeNo可选。股票代码或名称；不传则查询全市场公司事件。注意：这是公司事件/风险日历，不是宏观财经日历或产业大会日历。
limitNo返回事件数，默认 80，最大 300。
formatNocontent[0].text：默认1行 headline；markdown=完整 markdown 表格；json=完整 JSON。
endDateNo事件结束日期，支持 YYYY-MM-DD 或 YYYYMMDD；不传默认未来 180 天。
startDateNo事件开始日期，支持 YYYY-MM-DD 或 YYYYMMDD；不传默认近 90 天。
eventTypesNo事件类型过滤：unlock=限售解禁；holder_trade=股东增减持；repurchase=回购；dividend=分红除权；disclosure=财报披露计划。数组或逗号分隔字符串。
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.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds scope/aggregation context but nothing behavioral beyond that, such as coverage granularity or how events across the five types are merged or ordered.

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?

Front-loaded with the core purpose, but the '何时使用' clause repeats the opening sentence almost verbatim, roughly doubling the length without adding information. The duplicate exclusion note is also repeated in the code parameter description.

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 rich annotations, a full 7-parameter schema and an output schema present, the definition supplies enough for correct invocation: what it aggregates, the date-window defaults, and filter vocabulary. Remaining gaps are minor given the structured fields carry the rest.

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 every parameter (code, limit, format, dates, eventTypes, detailLevel) is already documented in the schema, including the enum values. The description's restatement of the eventTypes vocabulary adds no meaning beyond it, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

States a specific verb+resource: aggregating five named event types (限售解禁/股东增减持/回购/分红除权/财报披露计划) into a company event/risk calendar. It explicitly distinguishes itself from the macro financial calendar and industry-conference calendar, which maps onto the sibling tools macro_calendar and market_catalyst_calendar.

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?

Gives clear when-to-use contexts (短线排雷、事件驱动、盘前风险检查) and an explicit when-not (宏观财经日历/产业大会日历). It never names the alternative sibling tools directly, so routing is inferable rather than stated, which keeps it below a 5.

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