Skip to main content
Glama

AINDEX

What analysts expect of a stock

analyst_estimates
Read-only

A US stock's consensus EPS by quarter and year (range, number of estimates, recent revisions), price target (low, mean, high) with the buy, hold and sell count, the mean rating, and the last four quarters' earnings surprises. From Nasdaq.

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": {
      "ticker": "<ticker>"
    },
    "name": "analyst_estimates"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds two genuinely useful facts beyond that: coverage is limited to US stocks, and the data originates from Nasdaq (relevant for freshness and provenance). It says nothing about rate limits, authentication, or behavior for non-US or invalid tickers.

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?

One dense sentence, front-loaded with the resource being returned, followed by the field inventory and the data source. Every clause carries information. It is long but not padded, though it could be broken into a returned-fields list for faster scanning.

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 of describing return values, and it does so thoroughly across all the major field groups. For a one-parameter read-only lookup this is nearly sufficient; only the empty-result / invalid-ticker behavior and units for the price target remain unstated.

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 0% for the single required 'ticker' parameter, and the regex pattern only conveys the character class, not that it is an equity symbol. The description partially compensates by scoping the input to 'A US stock's', implying a US ticker rather than an arbitrary identifier. It does not state whether exchange suffixes or non-US listings are accepted, so the gap is narrowed but not closed.

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 and enumerates its contents precisely: consensus EPS by quarter and year, price target low/mean/high, buy/hold/sell counts, mean rating, and four quarters of earnings surprises. That is far more concrete than a generic 'get estimates'. It stops short of naming a verb or distinguishing itself from near neighbors like get_earnings or earnings_release, so a 4 rather than a 5.

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 no explicit when-to-use statement, no when-not-to-use, and no named alternative such as get_earnings for reported results versus forward expectations. Usage is only implied by the enumerated payload. An agent can infer the fit, but must do the routing work itself.

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