Skip to main content
Glama

Ashares Earnings Forecast

ashares_earnings_forecast
Read-onlyIdempotent

Company-issued earnings guidance (业绩预告) for a Chinese A-share stock, the company's own forecast announcements with predicted profit range (lower/upper bounds in CNY), year-over-year change %, forecast type (略增/预增/扭亏 etc.), and the company's stated reason. Answers '业绩预测', '业绩预告', 'earnings forecast/guidance for a China A-share company like 华工科技 000988'. Most recent reports first. Source: Eastmoney datacenter (keyless).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "000988"
    },
    "name": "ashares_earnings_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many forecast announcements to return, 1-20 (default 4, newest first).
symbolYes6-digit A-share code, e.g. "000988" (华工科技) or "600519" (贵州茅台).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"How many forecast announcements to return, 1–20 (default 4, newest first)."New value: +"How many forecast announcements to return, 1-20 (default 4, newest first)."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "symbol": "000988"
      +  },
      +  {
      +    "limit": 8,
      +    "symbol": "600519"
      +  }
      +]
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the description only needs to add context — and it does: it names the upstream source (Eastmoney datacenter) and, importantly, 'keyless' meaning no auth setup is required, plus a deterministic ordering rule ('most recent reports first'). It does not discuss empty-result behavior for uncovered companies or any rate limits.

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-loads the core definition, then the returnable fields, then query aliases and ordering/source. The bilingual query-alias clause is slightly repetitive but earns its place for retrieval matching; no sentence is padding.

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?

With no output schema, the description carries the burden and mostly discharges it by enumerating returned fields, ordering, and data source. A small gap remains around coverage (whether companies with no forecast simply return empty) and historical depth, but nothing needed to invoke the tool correctly is missing.

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% and both parameters (symbol as 6-digit code, limit as 1-20 default 4 newest-first) are fully documented in the schema. The description echoes symbol via the 000988 example and reinforces the newest-first ordering, but adds no syntax, format, or edge-case meaning the schema lacks, so the baseline of 3 applies.

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?

States a specific verb+resource: company-issued earnings guidance (业绩预告) for a Chinese A-share stock, with the precise payload enumerated (profit range bounds in CNY, YoY %, forecast type, stated reason). The qualifier 'company's own forecast announcements' separates it from the analyst-consensus sibling without the agent needing to open another schema.

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?

Gives concrete trigger context by listing the queries it answers ('业绩预测', '业绩预告', 'earnings forecast/guidance for a China A-share company like 华工科技 000988'), which helps an agent route Chinese and English phrasings here. It implies but never explicitly names an alternative such as analyst consensus, and states no exclusions.

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.