TipRanks

get_financials

Read-onlyIdempotent

Financial statements time series for a ticker, chart-ready. Each period is a flat ~25-field object spanning the income statement (revenue, gross / operating / EBITDA / net margins, EPS, R&D), the balance sheet (total assets, total debt, total equity, net debt, cash + short-term investments), the cash flow statement (operating cash flow, free cash flow, capex, dividends paid, buybacks), and two computed ratios (current ratio, debt-to-equity).

Margins are emitted as percentages — gross_margin_pct of 49.27
means 49.27%. Cash outflows (dividends_paid, buybacks) are
returned as negative numbers, matching the source convention.

Use for: "AAPL revenue and FCF over the last 10 years", "show
margins trend", "is net debt rising", "EPS growth", "R&D as %
of revenue".

Args:
    ticker: Stock ticker (e.g. 'AAPL', 'NVDA').
    period: 'annual' (default), 'quarterly', or 'ttm' (trailing
             twelve months). Annual periods extend ~9 years back;
             quarterly extends ~37 quarters back.
    count: Number of most-recent periods to return (default 5,
            max 40), ordered oldest-first inside the returned
            `periods` array.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`period`	No	'annual' (default), 'quarterly', or 'ttm'	annual
`ticker`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_financialsOutput",
-  "type": "object"
-}New value: +null

First observedJul 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already state readOnlyHint=true and idempotentHint=true, but the description adds valuable behavioral conventions beyond that: margins are percentages ('49.27 means 49.27%'), cash outflows are negative numbers ('matching the source convention'), period ranges (~9 years annual, ~37 quarters), and ordering (oldest-first). These details are not in annotations or schema.

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 detailed but every sentence serves a purpose: overview, field enumeration, formatting conventions, use cases, and parameter docs. It is front-loaded with the core purpose, then structured logically. No wasted words.

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?

Without an output schema, the description must explain the return value and does so thoroughly: it lists the ~25 fields, describes the flat structure, explains the computed ratios, and documents all three parameters with defaults and constraints. The tool's complexity is fully addressed.

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

Parameters5/5

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

Schema description coverage is only 33% (only period has any description). The description compensates fully: explains ticker with examples, period with allowed values and data history lengths, and count with default, max, and ordering semantics. This adds meaning far beyond the raw schema.

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?

Description opens with a specific statement: 'Financial statements time series for a ticker, chart-ready.' It names the resource (financial statements) and the action (get time series), and elaborates with a detailed field breakdown covering income statement, balance sheet, cash flow, and ratios, clearly distinguishing it from sibling quote/price tools.

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?

Provides explicit 'Use for' examples that map to common user intents ('AAPL revenue and FCF over the last 10 years', 'show margins trend', etc.). It does not explicitly name alternatives or state when not to use it, but the specificity of the examples makes the intended scenario obvious.

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

All TipRanks tools Inspect

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

Need Help?