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_feed

Recent A-share announcement feed (sorted by published_at desc). Filter by type slug (e.g. annual_report / equity_change / restructuring) or since lower bound. Use when surveying market-wide disclosures over a recent window — for a specific stock prefer announcements_stock. ⚠️ TIME: published_at is when the filing actually became visible — most A-share announcements go live after the previous session's close, so a filing dated "2026-08-27" by the exchange typically became readable at ~18:00 on 2026-08-26. The scheduled-disclosure stamp is the next calendar day at 00:00 and is returned separately as disclosure_date; never read disclosure_date as a publication time, and never conclude a filing was published at midnight.

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": "announcements_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
typeNo分类 slug 过滤(如 annual_report / equity_change / restructuring)。
limitNoMax items (1-200, default 50)
sinceNoISO datetime 下限(published_at >= since,按实际可见时刻过滤,非预约披露日)。**时区后缀必填**:北京时间用 2026-08-05T00:00:00+08:00,UTC 用 2026-08-05T00:00:00Z。不带时区会被拒绝——A 股业务时间是北京时间,静默按 UTC 解释会少算 8 小时的数据。
_spillNotrue=全量落盘,只回摘要与取数地址
offsetNoPagination offset
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the full disclosure burden, and it does address the highest-risk behavior: the publication-time semantics of `published_at` versus the scheduled `disclosure_date`, including the after-close go-live pattern and the warning not to read midnight stamps as publication time. It is silent on pagination behavior, result volume, and any rate/auth constraints for a 10-parameter, unpaginated-looking feed, which keeps it out of the top band.

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?

Purpose, guidance, and the time caveat are front-loaded in that order, which is the right priority. The time block is long and slightly repetitive ("never read `disclosure_date` as a publication time, and never conclude a filing was published at midnight"), but the redundancy buys real protection against a plausible misreading.

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 no output schema and 10 parameters, the description supplies the two things an agent most needs and cannot get structurally: which sibling to prefer and how to interpret the time fields in the results. It omits any picture of item contents beyond `disclosure_date` and says nothing about pagination depth, which leaves a modest gap for a feed tool.

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 baseline is 3. The description restates the `type` slug examples and the `since` lower-bound meaning that the schema already documents, and adds only the conceptual note that `since` filters on actual visibility rather than the scheduled disclosure day.

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 resource and scope ("Recent A-share announcement feed") plus the ordering guarantee ("sorted by published_at desc"), and explicitly distinguishes itself from the specific-stock sibling by naming `announcements_stock`. An agent can pick between the two without opening either schema.

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?

Gives an explicit use condition ("when surveying market-wide disclosures over a recent window") and an explicit alternative with the condition that selects it ("for a specific stock prefer `announcements_stock`"). It also names the two narrowing strategies (type slug or since lower bound) so filtering intent is 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