Skip to main content
Glama

Get forward estimates

get_forward_estimates

Read cached analyst consensus revenue/EPS estimates and available EPS revision percentages for one exact Bullrun ticker. A free background refresh checks supported symbols on demand, storing at most one snapshot per day; the first read may be empty. Fiscal periods and source currency are preserved. The configured feed does not provide EBITDA estimates, management guidance or revenue revisions. Forward P/E/PEG context uses the latest annual consensus snapshot only when quote and EPS currency units match. Does not change portfolios or user data.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum estimate rows to return.
tickerYesBullrun ticker, e.g. "AAPL", "CRWD", "SPGI". Use the listing ticker returned by search_stocks. US/European examples: AAPL, BMW, NESN. Most Asian listings keep their exchange suffix (6324.T, 0700.HK); some use bare codes (005930). Native or suffixed forms resolve only when one listing matches; search by company name or ISIN if unsure.
periodTypeNoReturn annual estimates, quarterly estimates, or both.both

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Bullrun ticker, e.g. \"AAPL\", \"CRWD\", \"SPGI\". Bullrun tickers: US and most European listings use the plain local symbol (AAPL, BMW, NESN, ABBN); most Asian and Indian listings keep their exchange suffix (Tokyo 6324.T, Hong Kong 0700.HK, Shanghai 600519.SS, Shenzhen 000001.SZ, Taiwan 2330.TW, Korea 000100.KS, Singapore D05.SI, India RELIANCE.NS), but some Japanese and Korean large caps are plain codes (Toyota 7203, Samsung 005930). Either form is resolved automatically when exactly one listing matches; use search_stocks to find a ticker by company name or ISIN."New value: +"Bullrun ticker, e.g. \"AAPL\", \"CRWD\", \"SPGI\". Use the listing ticker returned by search_stocks. US/European examples: AAPL, BMW, NESN. Most Asian listings keep their exchange suffix (6324.T, 0700.HK); some use bare codes (005930). Native or suffixed forms resolve only when one listing matches; search by company name or ISIN if unsure."
  2. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"The ticker exactly as listed on Bullrun, e.g. \"AAPL\", \"CRWD\", \"SPGI\"."New value: +"Bullrun ticker, e.g. \"AAPL\", \"CRWD\", \"SPGI\". Bullrun tickers: US and most European listings use the plain local symbol (AAPL, BMW, NESN, ABBN); most Asian and Indian listings keep their exchange suffix (Tokyo 6324.T, Hong Kong 0700.HK, Shanghai 600519.SS, Shenzhen 000001.SZ, Taiwan 2330.TW, Korea 000100.KS, Singapore D05.SI, India RELIANCE.NS), but some Japanese and Korean large caps are plain codes (Toyota 7203, Samsung 005930). Either form is resolved automatically when exactly one listing matches; use search_stocks to find a ticker by company name or ISIN."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses that data is cached with at most one snapshot per day, that a free background refresh runs on demand, that the first read may return nothing, and that fiscal periods and source currency are preserved. It also discloses feed limitations (no EBITDA, no management guidance, no revenue revisions) and the currency-unit precondition for forward P/E/PEG. The 'does not change portfolios or user data' line is consistent with destructiveHint=false even though readOnlyHint=false (the background refresh writes cache), so there is no contradiction.

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 and the key caveat (first read may be empty) before secondary details about feed gaps and currency matching. Dense but nearly every sentence carries decision-relevant information; the forward P/E/PEG sentence is the only one bordering on optional detail for an agent calling the tool.

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

Completeness5/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 still covers the important unknowns: what data classes are and are not available, that results may be empty on first call, that data is cached daily, and that currency units must match for derived valuation context. That is enough for an agent to call it correctly and interpret an empty response rather than retrying blindly.

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%, so ticker format, periodType enum and limit bounds are already fully documented in the schema. The description reinforces the 'one exact ticker' constraint and the fiscal-period/currency preservation, but adds no new semantics for limit or periodType. 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: reads cached analyst consensus revenue/EPS estimates plus EPS revision percentages for one exact Bullrun ticker. It is clearly distinguishable from siblings like get_stock_metrics, get_financial_history and get_valuation_model by naming the data domain (forward consensus) and the scope (one ticker, cached snapshots).

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 description gives useful operating context — cached data, background refresh, and a warning that the first read may be empty — which tells the agent when results may be absent. However, it never routes the agent to an alternative (e.g. get_valuation_model for forward P/E, or get_financial_history for actuals) and gives no explicit 'use this instead of X' guidance despite a dense sibling set.

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.