Skip to main content
Glama

wmshare_disclosures

Retrieve announcements, periodic reports, earnings events, dividend history, or workout events for stocks across CN, HK, and US markets using symbol, date range, and disclosure type filters.

Instructions

取公告、定期报告、业绩事件、分红历史或契约套利事件。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wmshare_disclosures"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo日期,格式 YYYY-MM-DD
kindNo披露族;高级公告查询请用 wmshare_noticenotice
beginNo日期,格式 YYYY-MM-DD
limitNo返回条数上限
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
symbolNo单票查询标的;部分全市场查询可空
windowNo相对窗口,如 3m/6m/1y 或正整数天数3m
keywordNo公告标题关键词
max_rowsNo单次返回的最大行数,硬上限 200

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only says data is fetched. It does not disclose that output can be a sample, count, or summary, how the relative `window` interacts with `begin`/`end`, how the market default resolves, or limits on rows returned—all of which materially affect behavior.

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?

A single short sentence with no filler, and the resource list is front-loaded. Its brevity is efficient, though for a ten-parameter tool the terseness leaves real gaps that other dimensions penalize.

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

Completeness2/5

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

For a tool with ten parameters, three output modes, relative and absolute date inputs, and market defaults, one sentence listing data families is not enough. Although an output schema exists and the input schema is fully documented, the description does not orient the agent to the tool's size or calling patterns.

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 explains every parameter, and the baseline is 3. The description adds modest value by enumerating resource families that correspond to the `kind` enum, but it does not clarify the interplay among `window`, `begin`/`end`, or `limit` vs `max_rows`.

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 gives a specific verb (取) plus an enumerated set of resource families (公告/定期报告/业绩事件/分红历史/契约套利事件) that maps onto the `kind` enum values. An agent can tell this is a multi-family disclosure retrieval tool, though nothing in the description distinguishes it from siblings such as wmshare_notice or wmshare_dividend.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no when-to-use or when-not-to-use guidance and names no alternative tool. The only routing hint (use wmshare_notice for advanced announcement queries) lives in the schema's `kind` field description, not in the tool description itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.