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

calendar_reports

Earnings-report disclosure window for one A-share: when the next periodic report is booked (next_report), whether today is its booked disclosure date (discloses_today), and the most recent report actually filed (latest_disclosed). Per-period status: scheduled | due_today | awaiting_confirmation (booked date passed, actual date not confirmed yet — T+1 lag or deferral, NOT a missed filing) | disclosed | unscheduled. Always read coverage first: schedule_pending means the exchange has not published the next period's calendar yet (released only ~5 days before period end) — a normal blackout, NOT 'this company does not report'; unknown means the name is absent from the calendar. T+1 data.

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": {
      "code": "<code>"
    },
    "name": "calendar_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
codeYesCanonical A-share code (e.g. SSE:600519)
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
periodsNoHow many recent report periods to return (1-12, default 4)
_max_bytesNo响应字节上限,默认约 50 KB
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and largely meets it: it discloses the T+1 data lag, pre-empts two likely misreadings of `status` (awaiting_confirmation is 'NOT a missed filing') and of `coverage` (schedule_pending is 'a normal blackout'), and explains the ~5-day publication window for exchange calendars. What is missing is any statement of the read-only/idempotent nature of the call or failure behavior for an unknown code (it only says 'unknown means the name is absent from the calendar').

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?

Front-loaded with the payload summary, then statuses, then the coverage gate, then the freshness caveat — a logical reading order with no filler sentences. It is dense and parenthetical-heavy (three inline 'NOT ...' clarifications), which slows parsing but each caveat guards against a plausible misinterpretation, so little is genuinely expendable.

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?

There is no output schema, so the description must explain return values itself, and it enumerates the key fields, both enums (status, coverage) and their edge meanings, plus the data-lag caveat. For a read-only single-stock calendar lookup with fully documented parameters, an agent can call this and interpret the response without further context.

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 schema already documents `code`, `periods`, and the underscore-prefixed projection controls; baseline is 3. The description adds no parameter-level meaning beyond 'one A-share' — it never mentions `periods` or how the lookback count interacts with the status/coverage semantics it explains at length.

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?

Names the exact resource ('Earnings-report disclosure window for one A-share') and enumerates the three payload elements (next_report, discloses_today, latest_disclosed), so an agent knows precisely what comes back. It never contrasts itself with the nearby alternatives (earnings_recent, financials_reports, calendar_upcoming), so sibling disambiguation is left to inference.

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

Usage Guidelines3/5

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

Usage is implied by the framing — this is a single-stock forward-looking schedule lookup, which is distinct from a filing-history tool. However there is no explicit when-to-use / when-not-to-use statement and no named alternative for the case where the agent actually needs filed financials rather than the calendar. The 'Always read coverage first' instruction guides output interpretation, not tool selection.

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