Skip to main content
Glama

FinBridge

Get US Company Financials (SEC XBRL)

get_edgar_financials
Read-only

Normalized annual (10-K) or quarterly (10-Q) financial statements for a US company, from SEC EDGAR XBRL company facts (US-GAAP). Values are raw USD (not scaled); eps_diluted is USD per share.

Not this tool for: Korean statements (get_dart_financials), a KR-vs-US pair on one screen (compare_financials_kr_us), or ranking many companies at once (query_db, which reads the stored table and covers KR/US/TW/JP/EU). This tool requests one US company's SEC XBRL company facts through the source adapter; results may be reused from a process-local cache for up to 24 hours. data_as_of.generated_at is response creation time, not source retrieval time. Peer comparisons use separately dated database snapshots.

Args:

  • company (required): ticker / company name / CIK (e.g. 'AAPL', 'Microsoft', '789019')

  • freq: 'annual' (default, from 10-K) or 'quarterly' (discrete Q1-Q3 from 10-Qs; Q4 is not reported separately)

  • periods: how many most-recent periods, 1-12 (default 3)

  • metrics: optional subset of [revenue, gross_profit, operating_income, net_income, eps_diluted, assets, liabilities, equity, cash_and_equivalents, operating_cash_flow] (default all)

  • response_format: 'markdown' (default) or 'json'

Returns NormalizedFinancials: {company:{name, id(CIK), ticker}, basis:'US-GAAP (10-K)', periods:[{period:'FY2024', fiscal_year, end, currency:'USD', metrics:{revenue, net_income, ...}}], notes}. periods are most-recent first; fiscal_year = calendar year of the period end date.

Examples:

  • "Apple's revenue and net income for the last 3 years" -> {company:'AAPL', metrics:['revenue','net_income']}

  • "MSFT last 4 quarters" -> {company:'MSFT', freq:'quarterly', periods:4}

Use when: you need US-GAAP fundamentals for a US-listed company. Don't use for: Korean companies (get_dart_financials), stock prices, or IFRS 20-F foreign private issuers (not supported).

Errors: unknown company -> use search_edgar_company first; companies without us-gaap XBRL facts (funds, 20-F filers) return an error explaining why.

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": {
      "company": "<company>"
    },
    "name": "get_edgar_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
freqNo'annual' = fiscal years from 10-K filings; 'quarterly' = discrete Q1-Q3 from 10-Q filingsannual
companyYesUS company: ticker (e.g. 'AAPL', 'BRK-B' or 'BRK.B'), company name, or CIK number
metricsNoOptional metric subset. Available: revenue, gross_profit, operating_income, net_income, eps_diluted, assets, liabilities, equity, cash_and_equivalents, operating_cash_flow. Default: all
periodsNoNumber of most-recent periods (default 3)
response_formatNo'markdown' for a table, 'json' for compact machine-readable outputmarkdown

Output Schema

NameRequiredDescriptionDefault
basisNo
notesNo
companyYes
periodsYes
data_as_ofNo
plan_limitNo
peer_comparisonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / basis / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / basis / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / company / additionalProperties
      Previous value: -trueNew value: +{}
    • removedOutput schema / properties / company / properties / cik / anyOf
      Removed value: -[
      -  {
      -    "type": [
      -      "string",
      -      "number"
      -    ]
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / company / properties / cik / type
      Added value: +[
      +  "string",
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / market / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / market / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / page_url / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / page_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / source / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / source / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / stock_code / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / stock_code / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / ticker / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / ticker / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / data_as_of / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / peer_comparison / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / periods / items / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / plan_limit / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed1 schema field changed
    • addedOutput schema / properties / notes
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. Changed3 schema fields changed
    • addedOutput schema / properties / data_as_of
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / peer_comparison
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / plan_limit
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {},
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover read-only/safe/open-world; the description adds genuinely non-obvious behavior: a process-local cache with up to 24h reuse, the caveat that data_as_of.generated_at is response creation time rather than retrieval time, that peer comparisons come from separately dated snapshots, and that Q4 is not reported separately. It also discloses failure modes for funds and 20-F filers.

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?

Well structured with front-loaded summary, exclusions, args, returns, examples and errors. Slight redundancy: the 'Use when / Don't use for' tail repeats the earlier 'Not this tool for' sentence and the Args list duplicates the schema.

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 5-param tool with an output schema, the description covers scope, units, cache staleness, period ordering, default behavior and error paths — everything an agent needs to call it correctly and interpret the response.

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 coverage is 100%, so the baseline applies; the Args block largely restates the schema (freq, periods, metrics, response_format). The only added semantics are on the value side (raw USD not scaled, eps_diluted in USD per share), which describes returns rather than parameter meaning.

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: normalized annual (10-K) or quarterly (10-Q) statements for a US company from SEC EDGAR XBRL company facts. It immediately names the sibling tools it is NOT (get_dart_financials, compare_financials_kr_us, query_db), so an agent can disambiguate without opening schemas.

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?

Explicit when-to-use ('US-GAAP fundamentals for a US-listed company') and when-not (Korean companies, stock prices, IFRS 20-F filers not supported), each paired with the alternative tool to use instead. Error routing is also specified: unknown company -> search_edgar_company first.

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.