Yahoo Finance MCP Server

Financial statements

get_financials

Read-only

Fetch income, balance, or cashflow statements for a Yahoo ticker or ISIN. Choose annual, quarterly, or trailing twelve months to see line items by reporting period.

Instructions

Get a financial statement for a Yahoo symbol.

Each row is a line item and each column a reporting period, most recent first.

Input Schema

Name	Required	Description	Default
`freq`	No	Reporting frequency: 'annual', 'quarterly', or 'ttm' (trailing twelve months, income and cashflow only).	annual
`symbol`	Yes	A Yahoo ticker or an ISIN, e.g. 'AAPL', 'SAP.DE' or 'US0378331005'. For a company name, use 'search' first.
`statement`	No	Which statement: 'income' (income statement), 'balance' (balance sheet), or 'cashflow' (cash flow).	income

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.8.6Oct 17, 2026
- removedInput schema / properties / freq / title
```
Removed value: -"Freq"
```
- removedInput schema / properties / statement / title
```
Removed value: -"Statement"
```
- removedInput schema / properties / symbol / title
```
Removed value: -"Symbol"
```
- removedInput schema / title
```
Removed value: -"get_financialsArguments"
```
- removedOutput schema / title
```
Removed value: -"get_financialsDictOutput"
```
Changed1 schema field changedv0.7.0Oct 1, 2026
- addedInput schema / properties / symbol / maxLength
```
Added value: +32
```

Changed2 schema fields changedv0.4.0Aug 18, 2026

changedInput schema / properties / freq / description

Previous value: -"Reporting frequency: 'annual', 'quarterly', or 'ttm' (trailing twelve months; income and cashflow only)."New value: +"Reporting frequency: 'annual', 'quarterly', or 'ttm' (trailing twelve months, income and cashflow only)."

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."

First observedv0.2.2Aug 2, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value by disclosing the return layout (rows are line items, columns are reporting periods, most recent first), but says nothing about frequency/statement interactions or limits.

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?

Two tight sentences with the purpose front-loaded and no filler. The second sentence earns its place by describing the data orientation, which is not obvious from the schema.

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 explain return values, and annotations plus full schema coverage handle safety and parameters. The layout note rounds it out; only minor usage-routing context is missing.

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 freq, symbol, and statement are all fully documented in the schema, including the 'ttm' restriction to income and cashflow. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 a financial statement'), which is clearly distinct from siblings like get_earnings, get_quote, and get_company_info. However, it never names an alternative, so differentiation is inferred from the resource noun rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use or when-not-to-use guidance and names no alternative tool. The useful routing hint ('For a company name, use search first') lives only in the symbol parameter's schema description, not in the tool description itself.

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