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_upcoming

KEY FIELDS (per item): event_kind (not kind), title, summary, expected_on + date_precision + window_end, entities[].entity_code (the canonical code lives here), entities[].role, importance (1–5), status, certainty, scope. Forward catalyst calendar for the whole A-share market: earnings disclosures, lock-up expiries, buyback deadlines, dividends, IPOs, LPR, macro / policy calendar, major tech conferences, US earnings for A-share supply chains, and forward milestones from broker research and newswires. Answers what is scheduled, never what happened. Filter with kinds (prefix wildcards like macro.*), scope, codes, importance_min, statuses. Pass precision=day unless you handle window_end yourself. ⚠️ 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

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
daysNoForward window in days (1-180, default 14). Ignored when date_to is given.
codesNoComma-separated canonical codes (max 200) to narrow to a portfolio
kindsNoComma-separated event_kind filter; prefix wildcards work, e.g. `earnings.disclosure,macro.*`. Kinds: earnings.disclosure, earnings.us_disclosure, ownership.lockup_expiry, buyback.plan_expiry, corp.dividend, ipo.subscription, ipo.listing, macro.data_release, macro.monetary, macro.lpr_release, policy.event, policy.regulation, policy.trade_measure, industry.expo, industry.event, corp.product_launch, corp.capacity_online, corp.price_change, corp.event
limitNoMax rows (1-1000, default 200). `total` is the true count in the window and is NOT capped by this; `truncated` flags that more exist.
scopeNoFilter by subject scope
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
date_toNoWindow end YYYY-MM-DD. Span is capped at 180 days and clamped if longer.
statusesNoComma-separated status set; defaults to `scheduled,postponed` (the two open states). Add `occurred` / `expired` to see what already passed.
date_fromNoWindow start YYYY-MM-DD (defaults to today)
precisionNo`day` = pinned to an actual day; `fuzzy` = period-only rows (`expected_on` is the window START). Omit for both; the two are disjoint. Pass `day` unless you handle `window_end`.
_max_bytesNo响应字节上限,默认约 50 KB
importance_minNoMinimum importance (1-5, 5 highest — e.g. FOMC)
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations, the definition does heavy lifting: it warns that non-day `date_precision` rows use `expected_on` as a window start, that `expired` means the window closed without confirmation rather than a non-event, and that `certainty: confirmed` on research-sourced rows is not an exchange filing. That is genuinely useful semantics. However, it says nothing about permissions, cost, or response shape/pagination behaviour beyond the schema's own `truncated`/`total` notes, so the disclosure is not complete.

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?

Dense but nearly zero waste: the field inventory, purpose statement, filter list, and two conditional warnings each carry distinct information. Warnings are marked with a clear symbol and placed directly after the invocation guidance, so the reader hits the dangerous misinterpretations before querying.

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

Completeness5/5

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

For a 16-parameter tool with no output schema, the definition supplies the missing return contract by listing the per-item fields and their caveats, and it resolves the highest-risk ambiguities (fuzzy date windows, expired vs cancelled, certainty sourcing). Nothing material to correct invocation or interpretation appears missing.

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%, so a baseline of 3 applies, but the description goes further: it explains the practical intent of `precision` (use `day` unless you handle `window_end`), the prefix-wildcard behaviour of `kinds`, and the default open status set. It also decodes key result fields (`event_kind` vs `kind`, `entities[].entity_code` as the canonical code), though much of the per-parameter detail duplicates the schema.

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 definition names a specific verb-plus-resource ('Forward catalyst calendar for the whole A-share market') and enumerates the event classes it covers (earnings disclosures, lock-ups, buybacks, dividends, IPOs, LPR, macro/policy, tech conferences). The line 'Answers what is scheduled, never what happened' cleanly separates it from history-oriented siblings such as events_timeline.

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

Usage Guidelines4/5

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

It gives concrete operating instructions: narrow with `kinds` (prefix wildcards), `scope`, `codes`, `importance_min`, `statuses`, and explicitly 'Pass `precision=day` unless you handle `window_end` yourself.' The forward-only scope implies when to prefer it over a past-events tool, but it never names an alternative tool or states an explicit exclusion boundary.

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