beatandraise.com SEC Filings

Get Financial History

get_financial_history

Read-onlyIdempotent

A company's financial statements from its last several 10-Ks or 10-Qs, in one call.

For trends (revenue, margins, cash flow over years or quarters) instead of calling get_financial_statements filing by filing. Returns each filing, newest first, with its statements as that filing presents them (the same text get_financial_statements gives). They are not combined into one table: a 10-K shows two or three years, so periods repeat across filings (the newest filing's figure is current; it may restate), and labels, line items and scale can differ between filings. Read the figures from each filing yourself.

Coverage: filings with XBRL, which the SEC phased in by company size: the largest companies from mid-2009, other large companies from mid-2010, all others from mid-2011. Earlier reports have no statements here (read a 10-K's Item 8 with get_filing_item); to have earlier years added, email support@beatandraise.com.

Args: cik: Company CIK (use search_companies to find it) period: "annual" (10-K, or a foreign filer's 20-F / 40-F; default 5 filings, max 10) or "quarterly" (10-Q, default 8, max 20; foreign filers report quarters on 6-K, not covered) statements: Optional subset: "income_statement", "balance_sheet", "cash_flow", "equity", "comprehensive_income". Ask for fewer to get more filings in one answer. limit: Number of filings to read before: Only filings filed on or before this date (YYYY-MM-DD), for history as of a past date fiscal_year: Only filings for this fiscal year, as the company states it on the filing (fiscal, not calendar: Medtronic's fiscal 2018 runs May 2017 to April 2018) fiscal_period: With or without fiscal_year: "Q1", "Q2", "Q3" (a 10-Q) or "FY" (the annual report). There is no Q4 filing: the fourth quarter is in the annual report, as the year. E.g. fiscal_year=2018, fiscal_period="Q1" returns that one 10-Q; fiscal_year=2018 with period="quarterly" returns its Q1-Q3. Each returned filing carries its fiscal_year and fiscal_period. include_tags: true to also get each statement as lines: every line with its XBRL tag (concept, axis members, unit) and its figures for the filing's own period (this quarter and year to date, or the balance sheet date), each with its value in full units, the text the page prints, a ref for check_citations and a highlight_url that opens the 10-K / 10-Q with that number marked. For building a spreadsheet model or citing figures: concept + members + unit identifies the same line in the next filing. Figures printed as a dash (zero) and filings before mid-2019 (no inline XBRL) have no ref or link; a filing's tags are added the night after it is filed (tags_note says why a statement has none). Responses are larger: ask for fewer statements or filings.

Input Schema

Name	Required	Default
`cik`	Yes
`limit`	No
`before`	No
`period`	No	annual
`statements`	No
`fiscal_year`	No
`include_tags`	No
`fiscal_period`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations supply the safety profile (readOnly, idempotent, openWorld), and the description adds genuinely new behavior: filings returned newest first, statements NOT merged into a single table, repeated periods and label/scale drift between filings, XBRL coverage phase-in dates, tag availability lagging one night after filing, and enlarged responses when include_tags is true.

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?

Purpose and the sibling comparison are front-loaded, and the Coverage and Args blocks are cleanly separated. It is long (~500 words), but nearly every sentence carries actionable information given 8 undocumented parameters; a few clauses on include_tags could be tightened.

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?

Despite having an output schema, the description still explains enough return shape (per-filing statements, lines with concept/members/unit/ref/highlight_url) for the agent to plan usage, and it covers the main failure modes — missing pre-2009 data, missing refs before mid-2019, missing tags on new filings.

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 0%, so the description must carry all parameter meaning — and it does: defaults and maxima for period/limit, the valid statements enum values, the YYYY-MM-DD format for before, fiscal-vs-calendar year with a Medtronic example, the absence of a Q4 filing, and the cost tradeoff of include_tags.

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?

States a specific verb and resource ('A company's financial statements from its last several 10-Ks or 10-Qs, in one call') and explicitly contrasts itself with the sibling it resembles ('instead of calling get_financial_statements filing by filing'). An agent can distinguish the two tools without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative (get_financial_statements) and the condition selecting this one (trend analysis across years/quarters). It also routes negative cases: pre-XBRL reports go to get_filing_item, and foreign filers' quarterly 6-K data is declared out of scope.

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

All beatandraise.com SEC Filings 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?