Skip to main content
Glama
Unofficial Yahoo Finance MCP Server

Unofficial Yahoo Finance MCP Server

Analyst estimates

get_estimates
Read-only

Retrieve forward analyst earnings and revenue estimates, EPS trends and revisions, and growth estimates for a Yahoo Finance equity symbol; returns an error for ETFs, funds, or crypto.

Instructions

Get forward analyst estimates for a Yahoo symbol.

Returns earnings and revenue estimates, EPS trend and revisions, and growth estimates (small tables keyed by period). Equity-only: an ETF, fund or crypto symbol answers with an error that says so. methodology applies to the three EPS tables, revenue and growth have one basis only.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_estimates"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesA Yahoo ticker or an ISIN, e.g. 'AAPL', 'SAP.DE' or 'US0378331005'. For a company name, use 'search' first.
methodologyNoEPS basis: 'gaap' (as reported) or 'normalized' (without one-off items). Omit for the basis Yahoo uses for the symbol, which differs between companies, so pick one to compare several. Each EPS row names its basis in `methodology`, which is Yahoo's own label when omitted and not always right. A basis Yahoo lacks for a symbol comes back empty or as null values.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / methodology
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "EPS basis: 'gaap' (as reported) or 'normalized' (without one-off items). Omit for the basis Yahoo uses for the symbol, which differs between companies, so pick one to compare several. Each EPS row names its basis in `methodology`, which is Yahoo's own label when omitted and not always right. A basis Yahoo lacks for a symbol comes back empty or as null values."
      +}
  2. Changed3 schema fields changedv0.8.6
    • removedInput schema / properties / symbol / title
      Removed value: -"Symbol"
    • removedInput schema / title
      Removed value: -"get_estimatesArguments"
    • removedOutput schema / title
      Removed value: -"get_estimatesDictOutput"
  3. Changed1 schema field changedv0.7.0
    • addedInput schema / properties / symbol / maxLength
      Added value: +32
  4. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / symbol / description
      Previous value: -"A native Yahoo Finance ticker symbol, e.g. 'AAPL', 'MSFT', 'SAP.DE', or 'BMW.DE'. This is NOT an ISIN, a WKN, or a company name, and must NOT be built by appending an exchange suffix to an ISIN (e.g. 'US0378331005.DE' is invalid). If you only have a name or ISIN, call the 'search' tool first and pass the 'symbol' value it returns."New value: +"A Yahoo ticker or an ISIN, e.g. 'AAPL', 'SAP.DE' or 'US0378331005'. For a company name, use 'search' first."
  5. First observedv0.2.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, and the description adds real substance beyond them: the output is 'small tables keyed by period', non-equity symbols fail with a self-describing error, and `methodology` scopes only to the three EPS tables. It stops short of noting any rate limits or whether empty tables indicate missing coverage versus missing data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the verb and resource, then returns, then the eligibility constraint, then the parameter scope note. No filler or restatement of the title.

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 an output schema present, the description needn't document return fields, and it supplies the two things that schema can't: the equity-only eligibility rule and the methodology blast radius. A note on how empty EPS tables should be interpreted would close the remaining gap.

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 schema already explains symbol formats and the gaap/normalized basis in depth, so the baseline is 3. The description adds a modest but real clarification — that methodology affects only the EPS tables while revenue and growth have a single basis — which is scope information the schema does not state.

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?

States a specific verb and resource ('Get forward analyst estimates for a Yahoo symbol') and enumerates the returned content: earnings and revenue estimates, EPS trend and revisions, growth estimates. That is clearly distinct from siblings like get_earnings or get_recommendations, though it never names those siblings to make the boundary explicit.

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?

Gives one hard usage constraint — equity-only, with ETFs, funds and crypto returning an explanatory error — which is genuinely useful routing information. It offers no guidance on when to prefer this over get_earnings, get_recommendations or get_upgrades_downgrades, so the agent must infer the split from names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.