Skip to main content
Glama

Analyst Forward Estimates

analyst_forward_estimates
Read-onlyIdempotent

Forward EPS consensus for one US stock, per fiscal quarter and fiscal year: mean, high, low, number of estimates, and the count of upward and downward revisions over the last 4 weeks. Use for "what does the Street expect AAPL to earn next quarter", "how many analysts estimate NVDA EPS". EPS only; no revenue consensus. Sourced live from Nasdaq's public analyst data.

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": "AAPL"
    },
    "name": "analyst_forward_estimates"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesUS ticker symbol, e.g. "AAPL", "NVDA", "AMGN".

Output Schema

NameRequiredDescriptionDefault
yearsYes
sourceNo
symbolYes
quartersYes
retrieved_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, so the safety profile is covered structurally. The description adds genuine value with data provenance ('sourced live from Nasdaq's public analyst data'), which tells the agent about freshness and reliability, but says nothing about latency, coverage limits, or what happens for tickers without analyst coverage.

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 what is returned before giving usage examples and scope exclusions; three sentences carry no filler. The metric enumeration is long but each item is substantive, so density is earned rather than padded.

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 lookup with an output schema and full annotations, the description covers scope, returned metrics, data source, and an explicit exclusion, which is enough to call it correctly. It leaves minor gaps around coverage edge cases and period/currency conventions.

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?

Single parameter with 100% schema coverage that already states 'US ticker symbol' with examples. The description reinforces the single-stock, US-only constraint implicitly, but adds no new meaning about ticker format, exchange suffixes, or invalid-symbol handling beyond the schema.

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?

Names a specific resource (forward EPS consensus) with explicit granularity (per fiscal quarter and fiscal year), lists the exact metrics returned, and carves out scope with 'EPS only; no revenue consensus', which separates it from revenue-oriented siblings without needing to name them.

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?

Provides two concrete natural-language query patterns that show exactly when to reach for it, plus a clear exclusion (no revenue consensus). It does not explicitly point to an alternative tool for revenue or price targets, so the routing guidance stops just short of a 5.

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.