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

earnings_recent

Scan A-share earnings pre-announcements filed in the last N days, newest first then YoY floor desc — the first-hand material for attributing a move to results rather than news flow. Filter by direction (positive|negative|uncertain), report_type, min_pct (YoY floor in percentage points), or codes to narrow to a portfolio. revision is computed against each name's FULL history, not just rows inside the window, so a downgrade filed today reads as revised_down even when its first version predates the window. Note min_pct also drops rows that have no percentage data.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
daysNoLookback window in days (1-90, default 7)
codesNoComma-separated canonical codes (max 200) to filter a portfolio
limitNoMax rows (1-1000, default 200)
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
min_pctNoMinimum YoY net-profit change (percentage points); also drops rows lacking percentage data
directionNoFilter by forecast direction (derived from type, not from the percentage)
_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

A3.9/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 does meaningful work: it discloses the sort order, that `revision` is computed against each name's full history rather than the window (a non-obvious semantic that would otherwise cause misreads), and that `min_pct` silently drops rows with no percentage data. It does not cover permissions, rate limits, or result-size behavior beyond what the schema itself declares.

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?

Four tight sentences, each carrying distinct information: scope and ordering, the filter surface, the revision caveat, and the min_pct side effect. The most load-bearing content (scope plus ordering) is front-loaded, and nothing is restated from the schema.

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 12-parameter read tool with no output schema, the description covers the domain-relevant parameters and the returned ordering, which is the minimum an agent needs to call it correctly. The gap is the absence of any indication of what fields each row carries beyond the incidental mention of `revision`, so the agent cannot plan downstream use without trial.

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 the baseline is 3, and the description clears that bar by adding real meaning the schema does not: `direction` is derived from forecast type rather than the percentage, `min_pct` is a YoY floor in percentage points that also drops null-percentage rows, and `codes` is framed as portfolio narrowing. The plumbing parameters (_jq, _spill, _fields, _max_bytes) are left entirely to the schema, which is acceptable given full coverage.

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 description names a specific verb and resource ('Scan A-share earnings pre-announcements filed in the last N days') and pins down default ordering ('newest first then YoY floor desc'), so the agent knows exactly what comes back and in what order. It only gestures at sibling differentiation via 'rather than news flow'; it never names earnings_show or announcements_feed as the route to detail or raw filings.

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?

There is a usable decision cue in 'the first-hand material for attributing a move to results rather than news flow', which tells the agent the analytical situation this tool serves. However, there is no explicit when-not, no prerequisites, and no named alternative for the cases this tool does not cover, leaving alternative routing implicit.

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