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_upcoming

Scan A-shares whose periodic report is booked for disclosure in the next N days, sorted by booked date — the overnight-risk screen for earnings season. Pass codes (comma-separated) to narrow to a portfolio, report_type to restrict the period. Only names not yet confirmed as disclosed are returned and the window starts today, so awaiting_confirmation names (booked date already passed) are deliberately excluded. Note each period's calendar is published only ~5 days before period end, so scanning well ahead of that returns few or no rows.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
daysNoForward window in days (1-90, default 7)
codesNoComma-separated canonical codes (max 200) to filter a portfolio; omit to scan the whole market
limitNoMax rows (1-1000, default 200)
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
report_typeNoRestrict to one report period type
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 behavioral burden and does well: it discloses the filtering rule (confirmed-disclosed and awaiting_confirmation names are excluded), the window start ('today'), the ordering (booked date), and a data-availability constraint (~5-day lead on period calendars). It omits read-only/rate-limit framing and any return shape, which keeps it below the top mark.

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?

It is a single dense paragraph that front-loads the core action and scope, then layers filtering and the timing caveat, with no filler sentences. It is on the long side for a block of prose, but each sentence adds distinct information.

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 scanner with no annotations and no output schema, the description covers what matters for correct invocation: window semantics, portfolio narrowing, period restriction, exclusion logic, and the publication-timing trap. The underscore-prefixed control parameters (_jq, _spill, _fields, etc.) are left to the schema, which documents them at full coverage, so the remaining gap is minor.

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 every parameter including ranges, defaults, and enums. The description reinforces `codes` as a portfolio filter and `report_type` as a period restriction, but adds little syntax or semantics beyond what the schema states. A baseline 3 is appropriate.

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 and resource ('Scan A-shares whose periodic report is booked for disclosure in the next N days') and pins down scope further with ordering ('sorted by booked date') and a use-case label ('the overnight-risk screen for earnings season'). The exclusion rule ('Only names not yet confirmed as disclosed are returned') separates it from tools that surface already-confirmed reports or awaiting_confirmation records, so an agent can tell what this tool is not.

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 usage: pass `codes` to narrow to a portfolio, `report_type` to restrict the period, and it warns that the calendar is published only ~5 days before period end, so scanning far ahead returns few or no rows. That timing caveat is unusually useful guidance. It stops short of naming a specific alternative tool or a hard when-not condition beyond the timing note.

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