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).

events_timeline

KEY FIELDS (per row in upcoming[] / past[]): event_kind (not kind), title, expected_on + date_precision + window_end, entities[].entity_code, importance, status. One A-share security's dated events as two lists: upcoming (nearest first) and past (most recent first, within the look-back). limit applies to each list separately. ⚠️ Only date_precision = day rows are pinned to a day; for week/month/quarter/half/year rows expected_on is the START of the window (window_end is the far edge) — never render it as the event date. ⚠️ expired does NOT mean it did not happen — the window closed without confirmation reaching us; cancelled means withdrawn. certainty: confirmed on a research-sourced row is not an exchange filing.

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": {
      "canonical_code": "<canonical_code>"
    },
    "name": "events_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
limitNoMax rows PER LIST (1-500, default 100) — upcoming and past are capped separately
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
past_daysNoLook-back window in days (1-365, default 90). The library only retains 90 days of past events, so a longer look-back simply returns nothing extra.
_max_bytesNo响应字节上限,默认约 50 KB
upcoming_daysNoForward window in days (1-365, default 180)
canonical_codeYesCanonical A-share code (e.g. SSE:600519)
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior5/5

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

With no annotations to lean on, the description still discloses the semantics that matter: list ordering, `limit` applying per list, the 90-day retention reality, and the critical caveat that `expected_on` is a window start for non-day precision and must not be rendered as the event date. The `expired` vs `cancelled` distinction and the `certainty: confirmed` sourcing caveat go well beyond what any schema could express.

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?

Dense with useful content and free of filler, but poorly front-loaded: it opens with a field inventory ("KEY FIELDS ... `event_kind` (not `kind`) ...") and only reaches the tool's actual purpose in the second sentence. A reader scanning for "what does this do" must read past the least important material first.

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?

For a 10-parameter, no-output-schema read tool, the description supplies the row shape, ordering, window semantics, and failure-mode vocabulary an agent needs to interpret results correctly. Gaps are minor: no explicit statement of what happens on an unknown code, and no guidance relative to overlapping siblings.

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 `limit`, `past_days`, `upcoming_days` and `canonical_code` are already documented; the description's "`limit` applies to each list separately" largely restates the schema. It adds no semantics for the window parameters beyond what the schema says. Baseline 3 is appropriate when the schema does the heavy lifting.

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 second sentence states the resource and shape precisely: "One A-share security's dated events as two lists: `upcoming` (nearest first) and `past` (most recent first, within the look-back)." An agent knows exactly what it gets. It does not, however, distinguish itself from the sibling `events_upcoming`, so the boundary is left to the agent.

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?

There is no when-to-use / when-not-to-use guidance and no reference to alternatives such as `events_upcoming` or `announcements_*`, despite obvious overlap with a sibling named for the same domain. Usage must be inferred from the name and the mention of look-back versus forward windows.

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