Skip to main content
Glama
This connector has been deprecated

Replaced by echopai-mcp.

Duplicate listing; superseded by io.github.echopai/echopai-mcp (official MCP Registry entry).

announcements_search

Hybrid search over A-share announcements: Chinese company name / 6-digit code / free-text keyword in one query (name or code → filter by stock; keyword → full-text relevance × recency over title + ai_summary + body start). Use when you DON'T have a canonical_code ("新华医疗 回购", "600587", "回购"); for a known stock prefer announcements_stock, for the market feed announcements_feed. ⚠️ TIME: published_at is when the filing became visible (usually the evening before the exchange date); disclosure_date (next day 00:00) is never a publication time.

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": {
      "q": "<q>"
    },
    "name": "announcements_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes名称 / 代码 / 关键词,可混合(如 "新华医疗 回购"、"600587"、"回购")
_jqNoJMESPath,对 data 求值(写 items[*].id)
typeNo分类 slug 过滤(与 feed 同集合)
limitNoMax items (1-200, default 50)
_spillNotrue=全量落盘,只回摘要与取数地址
offsetNoPagination offset
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
since_daysNo回看天数(1-1825,默认 90)。`limit` 在窗口之后截断,条目密集时实际返回范围会远小于所请求窗口,见响应的 `actual_window`,不足用 `offset` 翻页。⚠️ q 含关键词时按相关性排序而非时间倒序,本页是散落在窗口各处的高分条目:此时 `actual_window.contiguous=false` 且无 `covered_hours`,`earliest`/`latest` 只是本页极值,不代表这段时间已看全;要按时间连续通读改用 announcements_feed / announcements_stock。
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description still provides substantial operational detail: stock-filter versus full-text behavior, relevance-by-recency ranking, the searched fields, and the important distinction between `published_at` and `disclosure_date`. The read-only and non-destructive profile remains implicit in “search,” and response-window or truncation behavior is not summarized here, so it falls short of exhaustive behavioral disclosure.

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

Conciseness5/5

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

Three dense but purposeful sentences front-load the capability, then provide tool routing, and finish with a critical time-field warning. The examples and parenthetical details support correct invocation, and there is no filler or repetition of routine parameters.

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?

Together with the fully documented schema, the description provides enough information to select the tool and construct its required query correctly, including domain scope, alternatives, ranking behavior, and date semantics. Because there is no output schema, completeness would be improved by briefly describing the result envelope and surfacing the non-contiguous relevance-window behavior currently explained only under `since_days`.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, establishing a baseline of 3, but the description adds meaningful semantics for `q` beyond its schema: how each input form changes execution and which fields keyword search examines. It appropriately avoids repeating the already well-documented pagination, projection, and response-size parameters.

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?

The description precisely identifies the resource and operation: hybrid search over A-share announcements using a Chinese company name, six-digit code, free-text keyword, or a mixture. It further distinguishes the query modes by explaining that names and codes filter by stock while keywords use relevance and recency over specific announcement fields.

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

Usage Guidelines5/5

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

It gives an explicit selection condition—use this tool when a canonical_code is unavailable—and supplies concrete example queries. It also routes known-stock searches to `announcements_stock` and market-feed requests to `announcements_feed`, making the sibling choice clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources