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_show

Earnings pre-announcements and flash reports for one A-share. forecasts = mandatory guided ranges (net-profit floor/ceiling CNY + YoY); express = voluntary unaudited actuals. direction (positive / negative / uncertain) comes from the forecast TYPE, not the percentage (turnaround names have misleading YoY). Every revision is kept with revision (first / revised_up / revised_down / revised_flat); has_downward_revision flags a downgrade. ⚠️ Flash reports are voluntary and sparse — an absent express is normal.

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

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

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does add real semantics: `direction` derives from forecast TYPE rather than YoY percentage (turnaround names mislead), every revision is retained with a `revision` enum, and `has_downward_revision` flags downgrades. It stops short on operational behavior — no ordering of periods, no note on whether data can be missing for the whole `forecasts` block, no rate/limit context.

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?

Dense but front-loaded: resource and scope first, then field semantics, then the caveat. Every clause carries content; the use of backticks and the ⚠️ marker aids scanning, though the field-definition clustering makes it read like inner documentation rather than a call instruction.

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

Completeness3/5

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

With no output schema and no annotations, the description is the only source for return semantics, and it covers the key fields and the sparsity caveat well. It is incomplete on the mechanics an agent needs to call correctly — period ordering, what an empty `forecasts` implies, and how the framework parameters (`_jq`, `_fields`, `_spill`) interact with the described structures.

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 coverage is 100%, so the schema already documents `code` and `periods`, and the description adds nothing about parameter behavior — notably it never says what `periods` (1-12, default 4) does to the returned structures or ordering. Baseline 3 applies 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?

States a specific resource and scope: pre-announcements and flash reports for one A-share, and splits the payload into `forecasts` (mandatory guided ranges) vs `express` (voluntary unaudited actuals). That is far more informative than a restated title, though it never names or contrasts the sibling earnings_recent, which is presumably the nearest alternative.

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?

No when-to-use or when-not guidance, and no alternative is named — an agent cannot tell from this text why it would pick earnings_show over earnings_recent. The closing note that flash reports are voluntary and an absent `express` is normal is interpretive guidance for reading results, not selection guidance.

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