Skip to main content
Glama

Standardized financial statement

financials_standardized
Read-onlyIdempotent

Return one standardized statement (income statement, balance sheet, cash flow, or the supplemental statement with share counts and per-share figures) for a company, mapped to the FinancialMD concept template so line items are comparable across companies. Choose annual, quarterly, ltm or ytd periods and how many. Every cell is a value object with unit, currency, period, the known interval (when FinancialMD first and last knew this value), a restated flag and a proof that points at the filing, page and XBRL tag. as_of replays the statement as it was known on a date; original=true returns the first-reported version of each period; history=true returns every knowledge version of each period, oldest first, so restatements are visible. Use it for comparable statement numbers, trends over periods and the inputs of a model.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 5,
      "company": "ticker:AAPL",
      "statement": "income_statement",
      "period_type": "annual"
    },
    "name": "financials_standardized"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoKnowledge date or timestamp (YYYY-MM-DD or RFC 3339). The answer is what FinancialMD knew at that instant: only facts whose known interval contains as_of. Omit for the current view.
limitNoMaximum number of periods or items to return (default 10, at most 200).
companyYesCompany identifier: a FinancialMD id ("fmd_01H..."), an SEC CIK ("cik:320193"), or a ticker ("ticker:AAPL", optionally with the MIC "ticker:AAPL.XNAS"). A bare ticker like "AAPL" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI ("lei:IOG4E947OATN0KJYSD45") or its fmd_ id.
historyNoReturn every knowledge version of each period (oldest first). Mutually exclusive with original.
originalNoReturn the first-reported value of each period instead of the current one.
statementYesWhich financial statement. supplemental carries share counts (outstanding, weighted average) and per-share figures.
period_typeNoPeriod basis: annual (fiscal years), quarterly, semi_annual (half years: foreign filers that report on Form 20-F and furnish half-year figures on Form 6-K), ltm (last twelve months) or ytd (year to date). When a grid is empty, data.notes says why and meta.remedies names the calls that have rows.annual

Output Schema

NameRequiredDescriptionDefault
dataNoThe standardized statement grid: periods (most recent first) and rows with cells aligned to them.
metaNoRequest metadata: request_id, as_of, company resolution, coverage, pipeline_version, licence, terms, proof_base.
errorNoPresent only on isError results: the API error code and message plus remedy hints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / period_type / description
      Previous value: -"Period basis: annual (fiscal years), quarterly, ltm (last twelve months) or ytd (year to date)."New value: +"Period basis: annual (fiscal years), quarterly, semi_annual (half years: foreign filers that report on Form 20-F and furnish half-year figures on Form 6-K), ltm (last twelve months) or ytd (year to date). When a grid is empty, data.notes says why and meta.remedies names the calls that have rows."
    • changedInput schema / properties / period_type / enum
      Previous value: -[
      -  "annual",
      -  "quarterly",
      -  "ltm",
      -  "ytd"
      -]New value: +[
      +  "annual",
      +  "quarterly",
      +  "semi_annual",
      +  "ltm",
      +  "ytd"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / company / description
      Previous value: -"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL."New value: +"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI (\"lei:IOG4E947OATN0KJYSD45\") or its fmd_ id."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a read-only, idempotent, closed-world tool, and the description adds substantial behavior beyond that: each cell carries unit, currency, period, a known interval, a restated flag and a proof pointer to filing/page/XBRL tag; as_of filters facts by knowledge interval; history returns every knowledge version oldest first so restatements surface. That is exactly the kind of provenance detail an agent needs to trust and interpret results.

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?

It is dense but front-loaded, starting with what is returned, then period selection, then cell shape, then the versioning flags, then usage. A couple of clauses overlap with structured data (the per-cell value object fields largely mirror the output schema, and original/history are already in the schema), and 'annual, quarterly, ltm or ytd' omits semi_annual, which the schema supports.

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 7-parameter tool with an output schema, the definition covers the statement choice, period basis, count, versioning semantics and the provenance of returned values. The empty-result case is even handled through the period_type text pointing at data.notes and meta.remedies, so an agent has what it needs to call and interpret correctly.

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% and the schema itself documents every parameter well, so the baseline is 3. The description adds genuine meaning on top: it frames as_of as replaying the statement as known on a date, original as first-reported, and history as all knowledge versions ordered oldest-first for restatement visibility, which clarifies intent rather than restating types.

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?

The description opens with a specific verb and resource ('Return one standardized statement') and enumerates the exact statement variants, then adds the defining trait that separates it from an as-reported view: line items are mapped to the FinancialMD concept template so they are comparable across companies. An agent can tell precisely what this returns.

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?

It gives an explicit positive usage clause ('Use it for comparable statement numbers, trends over periods and the inputs of a model') and the per-flag conditions (as_of for point-in-time replay, original for first-reported, history for restatement visibility). It never states a when-not or names the as-reported alternative, so the exclusion side is left to inference.

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.

Resources