Livermore

Financial statements (XBRL)

get_financials

Read-onlyIdempotent

Financial statements of one company from the XBRL data in its 10-K, 10-Q, 20-F and 40-F filings (SEC companyfacts), newest period first: income statement (revenue, cost_of_revenue, gross_profit, operating_expenses, rd_expense, sga_expense, operating_income, interest_expense, tax_expense, net_income, eps_basic, eps_diluted, shares_basic, shares_diluted), balance sheet (cash_and_equivalents ... total_assets, total_liabilities, total_equity including minority interest), cash flow (operating_cash_flow, capex, free_cash_flow = operating cash flow minus capex, dividends_paid, share_buybacks, ..., depreciation_amortization, stock_based_compensation) and the cover-page shares outstanding (shares, with change_1y_pct). period=annual gives fiscal years (FY), quarterly gives single fiscal quarters (Q1-Q4). IMPORTANT: amounts are in the company's reporting currency (currency, for example TWD for TSMC), not US dollars; for other currencies usd_rate gives US dollars per unit: multiply income statement and cash flow amounts by usd_rate.average and balance sheet amounts by usd_rate.period_end. EPS is in that currency per share. Each period has its filing (form, filed_date, accession, sec_url), reported_date (the earnings 8-K, Item 2.02), margins (gross, operating and net margin, stock-based compensation as a percent of revenue) and yoy_pct (growth against the same fiscal period a year earlier). Numbers are as filed in each period's original report or its amendment. Known gaps: foreign companies (20-F, 40-F) have annual statements only; EPS and share counts are not adjusted for stock splits (stock_splits lists the splits in the range); for ADRs EPS is per ordinary share, not per ADS; Q4 and single-quarter cash flows are mostly derived by subtraction (listed in derived); banks' revenue may be interest income only; companies with several share classes may have no EPS or cover-page share count. note explains what applies to this company, including why there are no statements (ETFs and funds have none). No stock prices are returned and no valuation ratios are computed; get_stock has the company's market cap in USD (convert foreign-currency statements with usd_rate before comparing).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Number of periods, newest first: default 5 for annual, 8 for quarterly, at most 40.
`period`	No	annual = fiscal years (default); quarterly = single fiscal quarters.	annual
`ticker`	Yes	Stock ticker, e.g. AAPL or BRK.B (share classes use a dot; BRK-B also works).
`statements`	No	Which parts to return: income, balance, cash_flow, shares (cover-page shares outstanding). Default all, e.g. ["income"].

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes
`period`	Yes
`company`	Yes
`periods`	Yes
`coverage`	Yes
`currency`	Yes	Reporting currency of the latest period (ISO 4217). Amounts are in this currency, not USD.
`statements`	Yes
`stock_splits`	Yes
`shares_outstanding`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 8, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Far exceeds the annotations (readOnly/idempotent/non-destructive/closed-world): it discloses non-USD reporting currency and the usd_rate.average vs period_end conversion rules, filing/amendment provenance, Q4/single-quarter cash flows being derived by subtraction, unadjusted split/EPS caveats, ADR per-ordinary-share EPS, bank revenue caveats, multi-class share gaps, and the meaning of `note`.

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

Conciseness3/5

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

Front-loaded and information-dense, but the long parenthetical enumerations of individual line items (many with ellipses) are heavy and partially redundant given an output schema exists. A tighter description could carry the same semantic load with less bulk.

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?

For a complex, quirky data tool the description covers the gaps that matter: currency conversion, derived periods, split/ADR/bank/multi-class exceptions, amendments, and when no statements exist. Since an output schema exists, return-value shape needn't be re-explained, and nothing an agent needs to interpret results is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: it spells out that period=annual yields fiscal years and quarterly yields single fiscal quarters, what each `statements` value contains, and the currency semantics that govern how returned values must be interpreted.

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 specific verb+resource+scope: financial statements of one company sourced from XBRL in 10-K/10-Q/20-F/40-F SEC companyfacts. It names the concrete sections (income, balance, cash flow, shares) and explicitly distinguishes itself from get_stock for prices/valuation, so an agent can identify it without opening the schema.

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?

Gives clear operating context: period=annual vs quarterly semantics, statements selection, and explicitly routes the agent elsewhere for market cap ('get_stock has the company's market cap in USD'). It stops short of explicit when-not-to-use-it exclusions beyond the note about ETFs/funds having no statements, so not a full 5.

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

All Livermore 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?