Skip to main content
Glama

Fintel Discovery — Financial Intelligence for AI Agents

by io.github.findimitrov
OverviewDiscussionsAdmin

Get Financial Statements

GetFinancials
Read-onlyIdempotent
    Fetch income statement, cash flow statement, or balance sheet for a stock.
    Returns up to 4 years of annual data or 4 quarters of quarterly data,
    transposed so each row is one reporting period.

    Use this tool when:
    - You need revenue, net income, EPS, or operating margins
    - You want cash flow from operations, CapEx, or free cash flow
    - You need total assets, debt, equity, or liquidity ratios
    - You are doing fundamental analysis on a stock

    statement options: 'income', 'cashflow', 'balance'.
    freq options: 'yearly', 'quarterly', 'trailing' (TTM, income only).

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

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the description correctly focuses on extra behavioral detail: results are transposed with one row per reporting period, capped at 4 years/4 quarters, and the 'trailing' frequency is income-only. It also discloses the data source (Yahoo Finance) and that no API key is required, which covers authentication expectations.

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 cleanly structured: purpose, output behavior, when-to-use bullets, compact option enums, then source attribution. Each block has a distinct job and there is no redundant filler, so the length is justified.

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 read-only financial-data fetcher with an output schema, the description covers the essential surface: what statements can be retrieved, what frequencies and limits apply, the output orientation, and the source. The only minor gap is the lack of an explicit mention of the 'symbol' parameter, but that is easily inferred.

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

Parameters4/5

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

Schema description coverage is 0% at the top level, so the description must carry the parameter-semantics burden. It does a strong job for the two core knobs—'statement' and 'freq'—by listing their exact options and adding the TTM income-only constraint, but it never names 'symbol' explicitly, leaving that to be inferred from 'for a stock.'

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?

Opens with a precise verb and resource: 'Fetch income statement, cash flow statement, or balance sheet for a stock,' which immediately distinguishes it from sibling tools such as GetPriceHistory or GetDividendsAndSplits. It also names the three statement types and the data scope, so an agent knows exactly what domain this tool covers.

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?

The dedicated 'Use this tool when' section gives concrete triggers (revenue, EPS, cash flow, CapEx, balance sheet ratios, fundamental analysis), which is strong explicit guidance. It does not state when not to use the tool or point to alternative sibling tools, so it stops short of a perfect 5.

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