Skip to main content
Glama

As-reported financial statement

financials_as_reported
Read-onlyIdempotent

Return a statement exactly as the filer presented it: the company's own line-item labels, XBRL taxonomy and tags, dimensions, and the values with proof. Use it when the standardized template hides a detail you need (an unusual line, a segment axis, a footnote-level item) or when you must quote the filer's own wording. Supports as_of for point-in-time replay.

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": 2,
      "company": "ticker:AAPL",
      "statement": "income_statement",
      "period_type": "annual"
    },
    "name": "financials_as_reported"
  }
}

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 4, at most 40).
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 filing's version of each cell ({ versions }, oldest first) instead of the latest one.
statementYesWhich financial statement.
period_typeNoPeriod basis: annual, quarterly or semi_annual (half years; as-reported facts are not derived into ltm or ytd).annual

Output Schema

NameRequiredDescriptionDefault
dataNoThe as-reported grid: periods (most recent first) and one row per filed line { taxonomy, tag, label, dims, unit, display_order, is_subtotal, concept_id, cells }.
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 or quarterly (as-reported facts are not derived into ltm or ytd)."New value: +"Period basis: annual, quarterly or semi_annual (half years; as-reported facts are not derived into ltm or ytd)."
    • changedInput schema / properties / period_type / enum
      Previous value: -[
      -  "annual",
      -  "quarterly"
      -]New value: +[
      +  "annual",
      +  "quarterly",
      +  "semi_annual"
      +]
  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.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: results are unnormalized filer presentation, include XBRL taxonomy/tags and dimension axes, and 'as_of' enables point-in-time replay rather than a live view. It stops short of discussing pagination or how large statements are truncated by 'limit'.

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?

Three tightly packed sentences, front-loaded with the core definition before the when-to-use clause and the optional replay note. The parenthetical examples of hidden details earn their space by making the routing criterion concrete, and there is no redundant restatement of the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is correctly omitted, and the safety profile is covered by annotations. What remains missing is minor: no mention of what 'history' returns at the description level or how 'limit' interacts with multi-period statements, though both are documented in the 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 100%, so every parameter (as_of, limit, company, history, statement, period_type) is already fully documented upstream. The description only reinforces 'as_of' for point-in-time replay and does not add syntax, defaults, or interaction rules for 'history' or 'limit'. Baseline 3 is appropriate when the schema carries the semantics.

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 a statement exactly as the filer presented it', then enumerates what makes it distinct (filer's own line-item labels, XBRL taxonomy and tags, dimensions, values with proof). This clearly separates it from the standardized-template sibling without the agent needing to open 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?

It states explicitly when to use it ('when the standardized template hides a detail you need (an unusual line, a segment axis, a footnote-level item)') and when the filer's wording must be quoted. The alternative — the standardized template — is named implicitly as the default, so the routing decision is explicit.

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