Skip to main content
Glama

Fintel Discovery — Financial Intelligence for AI Agents

by io.github.findimitrov
OverviewDiscussionsAdmin

Get Earnings History & Estimates

GetEarningsHistory
Read-onlyIdempotent
    Fetch earnings history (EPS actual vs estimate, surprise %) and upcoming
    earnings dates with consensus estimates. Also returns forward EPS estimates
    by quarter and fiscal year.

    Use this tool when:
    - You want to see how a company has performed vs EPS expectations
    - You need the next earnings date and the consensus estimate
    - You are analyzing earnings surprise trends or growth trajectory

    Returns three sections: earnings_history, earnings_dates, earnings_estimate.

    Source: Yahoo Finance via yfinance. No API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / EarningsParams / properties / mcp_prompt_id / default
      Previous value: -"f258bd16-f060-4e4a-a55d-221a0484866d"New value: +"05525087-35e9-4aac-b06d-6d88ce386b2e"
  2. Changed1 schema field changed
    • changedInput schema / $defs / EarningsParams / properties / mcp_prompt_id / default
      Previous value: -"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"New value: +"f258bd16-f060-4e4a-a55d-221a0484866d"
  3. Changed1 schema field changed
    • changedInput schema / $defs / EarningsParams / properties / mcp_prompt_id / default
      Previous value: -"d9f77642-e017-4785-9150-e658c2dba3a0"New value: +"5f4db44b-e5cc-4f3a-8da3-ac591a019c81"
  4. Changed1 schema field changed
    • changedInput schema / $defs / EarningsParams / properties / mcp_prompt_id / default
      Previous value: -"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"New value: +"d9f77642-e017-4785-9150-e658c2dba3a0"
  5. Changed1 schema field changed
    • changedInput schema / $defs / EarningsParams / properties / mcp_prompt_id / default
      Previous value: -"3775b46a-5aa8-4586-af57-2453c8bcd08c"New value: +"dbe99169-c071-4ed4-9ae9-8bbfb9a88ad8"
  6. Changed1 schema field changed
    • changedInput schema / $defs / EarningsParams / properties / mcp_prompt_id / default
      Previous value: -"d81a5175-11e9-494a-baa5-71d4ffad4ab9"New value: +"3775b46a-5aa8-4586-af57-2453c8bcd08c"
  7. Changed1 schema field changed
    • changedInput schema / $defs / EarningsParams / properties / mcp_prompt_id / default
      Previous value: -"9e7f8798-7d22-4378-b93d-179c6f8cb854"New value: +"d81a5175-11e9-494a-baa5-71d4ffad4ab9"
  8. Changed1 schema field changed
    • changedInput schema / $defs / EarningsParams / properties / mcp_prompt_id / default
      Previous value: -"9919ff85-e960-472f-863b-3de4c5abed9f"New value: +"9e7f8798-7d22-4378-b93d-179c6f8cb854"
  9. Changed1 schema field changed
    • changedInput schema / $defs / EarningsParams / properties / mcp_prompt_id / default
      Previous value: -"38452924-d5df-4668-b51c-d7cd5acabc09"New value: +"9919ff85-e960-472f-863b-3de4c5abed9f"
  10. Changed1 schema field changed
    • changedInput schema / $defs / EarningsParams / properties / mcp_prompt_id / default
      Previous value: -"fa72f604-6239-428b-81df-11f07c2c8d00"New value: +"38452924-d5df-4668-b51c-d7cd5acabc09"
  11. Changed1 schema field changed
    • changedInput schema / $defs / EarningsParams / properties / mcp_prompt_id / default
      Previous value: -"7b866f24-13ab-4e54-8d3a-f775612c393f"New value: +"fa72f604-6239-428b-81df-11f07c2c8d00"
  12. First observed

TDQS

A3.8/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=false. The description adds useful context beyond those annotations: the data source (Yahoo Finance via yfinance), that no API key is required, and the three return sections.

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?

The description is front-loaded with the core capability, then use cases, then return structure and source. It is appropriately sized with no redundant 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?

An output schema exists, so explaining return values is not strictly required, but the description helpfully names the three returned sections. It is complete enough for the core earnings-history use case, though it does not address the broader set of schema parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% according to the context signals, and the description does not mention any parameter such as symbol, limit, wholesaler_ids, or source_resource_id. It therefore fails to compensate for undocumented parameters and leaves the agent with no description-level guidance on invocation arguments.

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 states a specific verb and resource set: fetch earnings history (EPS actual vs estimate, surprise %), upcoming earnings dates with consensus estimates, and forward EPS estimates. It is clear about what the tool does, though it does not explicitly name sibling alternatives such as GetFinancials or GetAnalystRatings.

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?

It gives an explicit 'Use this tool when' list covering performance vs expectations, next earnings date, and surprise trend analysis. It does not state when not to use this tool or name alternative tools for overlapping needs.

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

All Fintel Discovery — Financial Intelligence for AI Agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources