Skip to main content
Glama

Financial statements as filed

get_financials
Read-only

Returns a company's income statement, balance sheet and cash flow as filed with the SEC (XBRL): the last 12 calendar quarters or 6 fiscal years, each period with its filing. statement: 'breakdowns' gives revenue by segment, geography and product and the customers it discloses; 'outlook' its own guidance, actuals against it and an estimated next earnings date. A null is a line not filed: report it as unknown; howToRead in the answer says the rest. A 20-F filer has fiscal years, plus quarters from its 6-K releases (unaudited). A pre-IPO company (e.g. 'anthropic') returns its prospectus statements, by half year. Use it for revenue, earnings, balance sheet or cash flow over several periods.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
basisNoquarterly (default for a listed company: last 12 calendar quarters), half (half years: only for a company before its IPO, where it is the default) or annual (last 6 fiscal years).
symbolYesTicker or company name, e.g. NVDA, AMD, ASML, 'nvidia', 'taiwan semiconductor'. Case-insensitive.
statementNoincome, balance, cashflow, breakdowns (revenue by segment, geography and product, and customer concentration), outlook (the company's guidance, actuals against it, next earnings date) or all (default all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / basis / description
      Previous value: -"quarterly (default for a listed company: last 12 calendar quarters), half (half years: a company before its IPO only — its default) or annual (last 6 fiscal years)."New value: +"quarterly (default for a listed company: last 12 calendar quarters), half (half years: only for a company before its IPO, where it is the default) or annual (last 6 fiscal years)."
  2. Changed2 schema fields changed
    • changedInput schema / properties / basis / description
      Previous value: -"quarterly (default: last 12 calendar quarters) or annual (last 6 fiscal years)."New value: +"quarterly (default for a listed company: last 12 calendar quarters), half (half years: a company before its IPO only — its default) or annual (last 6 fiscal years)."
    • changedInput schema / properties / basis / enum
      Previous value: -[
      -  "quarterly",
      -  "annual"
      -]New value: +[
      +  "quarterly",
      +  "half",
      +  "annual"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / statement / description
      Previous value: -"income, balance, cashflow, breakdowns (revenue by segment, geography and product, and customer concentration) or all (default all)."New value: +"income, balance, cashflow, breakdowns (revenue by segment, geography and product, and customer concentration), outlook (the company's guidance, actuals against it, next earnings date) or all (default all)."
    • changedInput schema / properties / statement / enum
      Previous value: -[
      -  "income",
      -  "balance",
      -  "cashflow",
      -  "breakdowns",
      -  "all"
      -]New value: +[
      +  "income",
      +  "balance",
      +  "cashflow",
      +  "breakdowns",
      +  "outlook",
      +  "all"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / statement / description
      Previous value: -"income, balance, cashflow or all (default all)."New value: +"income, balance, cashflow, breakdowns (revenue by segment, geography and product, and customer concentration) or all (default all)."
    • changedInput schema / properties / statement / enum
      Previous value: -[
      -  "income",
      -  "balance",
      -  "cashflow",
      -  "all"
      -]New value: +[
      +  "income",
      +  "balance",
      +  "cashflow",
      +  "breakdowns",
      +  "all"
      +]
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond annotations, the description discloses important behavior: the data is as-filed XBRL, coverage is 12 calendar quarters or 6 fiscal years, nulls mean unfiled lines and should be reported as unknown, and howToRead provides further guidance. It also explains how 20-F filers and pre-IPO companies are handled, including unaudited 6-K quarters and prospectus statements by half year.

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 dense but front-loaded: it leads with the return scope, then covers statement variants, null handling, filer-type differences and usage. Every sentence adds operational value for a complex financial data tool.

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?

Given the tool's complexity, complete input schema and read-only annotations, the description is complete enough to call correctly. It covers coverage periods, special filer cases, null semantics, statement variants, and intended use without needing an output schema.

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 already 100%, and the description largely restates the enum meanings for statement and basis rather than adding substantial new parameter semantics. It adds slight nuance such as 'estimated next earnings date' and 'customers it discloses,' but the schema already carries the detailed parameter documentation.

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?

The description states a specific verb and resource: returns a company's income statement, balance sheet and cash flow as filed with the SEC in XBRL, with exact coverage periods. It is clear what the tool does, but it does not explicitly name or distinguish itself from siblings such as get_filings or get_company.

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 final sentence gives clear usage context: 'Use it for revenue, earnings, balance sheet or cash flow over several periods.' Special cases for 20-F filers and pre-IPO companies further guide applicability, but there is no explicit when-not-to-use or named alternative for raw filings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.