Skip to main content
Glama

wmshare_notice

Query market announcements by category, date, or symbol, and check buyback or reduction signals for a stock. Returns lists, counts, or summaries for CN, HK, and US markets.

Instructions

取公告列表、按类别/日期查询、单票区间和回购/减持布尔信号。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "wmshare_notice"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo日期,格式 YYYY-MM-DD
dateNoon_date 需要的 YYYY-MM-DD 日期
beginNo日期,格式 YYYY-MM-DD
limitNo返回条数上限
actionYes公告高级查询动作
marketNo目标市场 cn/hk/us;缺省用 server 配置市场
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
symbolNo标的代码;recent/by_category/on_date 可空
windowNo相对窗口,如 3m/6m/1y3m
keywordNo公告标题关键词
categoryNoby_category 需要的公告类别
max_rowsNo单次返回的最大行数,硬上限 200

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It reveals only that some outputs are boolean signals for buyback/reduction; it says nothing about read-only safety, permission or auth requirements, pagination/row limits, or how the sample/count/summary output modes behave, forcing the agent to dig into the schema.

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?

It is a single front-loaded sentence with no filler, which is good. But cramming seven distinct query capabilities into one comma-separated clause gives the agent no structure to map them onto the action enum.

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 12-parameter tool with seven action modes and no annotations, the description should explain the action modes and their required parameters. It does not, and relies entirely on the schema and output schema to fill the gaps.

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?

With 100% schema description coverage, the schema already documents every parameter, so the baseline of 3 applies. The description hints at category, date and symbol filtering but adds no syntax, default or interaction details beyond what the schema already states.

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

Purpose3/5

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

The description names verbs and a resource ('取公告列表', query by category/date, buyback/reduction boolean signals), so the subject matter is identifiable as a notice query tool. However, it lists capabilities as a comma-joined string without stating a primary purpose or distinguishing itself from sibling tools such as wmshare_disclosures or wmshare_corporate, leaving the agent to infer scope.

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 mentions query modes but never says when to use one mode versus another, nor does it name any alternative tool or exclusion condition. There is no guidance on prerequisites such as which market or symbol is required for a given mode.

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