Skip to main content
Glama

Ashares Analyst Consensus

ashares_analyst_consensus
Read-onlyIdempotent

Analyst consensus estimates (盈利预测) for a Chinese A-share stock, per forecast year: consensus EPS, P/E at current price, net profit attributable to parent (归母净利润), and total operating revenue, in CNY. Answers "analyst estimates / 盈利预测 / forecast EPS for a China A-share like 000988". 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": "300750"
    },
    "name": "ashares_analyst_consensus"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes6-digit A-share code, e.g. "000988" or "300750" (宁德时代).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "symbol": "300750"
      +  }
      +]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: data provenance (Eastmoney datacenter), keyless access (no credential needed), currency (CNY), and result granularity (per forecast year). It does not describe what happens for an unknown or delisted code, which keeps it off a 5.

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?

Two sentences, front-loaded with the resource and its returned fields, then the query-matching line. The example-query sentence partly restates the first but earns its place by supplying Chinese keyword aliases for retrieval matching. No filler.

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 one-parameter, read-only lookup with no output schema, the definition covers source, currency, units of analysis, and trigger intent — enough for correct invocation. The only real gap is disambiguation from the earnings_forecast sibling and behavior on invalid symbols.

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% and the single parameter is already documented as a 6-digit A-share code with an example (300750 / 宁德时代). The description reinforces the A-share constraint and repeats an example, but adds no format, normalization, or edge-case meaning beyond the schema. Baseline 3 applies.

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 resource (analyst consensus estimates / 盈利预测) for a specific asset class (Chinese A-share) and enumerates exactly what is returned: consensus EPS, P/E at current price, net profit attributable to parent, and total operating revenue. That is far more than a restatement of the name. It stops short of 5 because a near-identical sibling, ashares_earnings_forecast, exists and is never distinguished from this tool.

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?

The line 'Answers "analyst estimates / 盈利预测 / forecast EPS for a China A-share like 000988"' gives concrete trigger phrasing and keyword coverage, so an agent knows when the tool is a fit. However, there is no guidance on when NOT to use it and no named alternative, which matters given the overlapping a shares_earnings_forecast sibling.

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.