Edgar

Edgar Company Facts

edgar_company_facts

Read-onlyIdempotent

AUTHORITATIVE full XBRL fundamentals dump for a US public company. Send the company as cik — that argument takes a TICKER ("NVDA") or a CIK ("320193"), and ticker / ticker_or_cik are accepted as aliases for it. Returns every reported financial metric (hundreds of concepts: revenue, net income, assets, liabilities, EPS, cash flow lines, segment breakdowns) with annual and historical values pulled straight from the company's SEC filings — the official numbers, not estimates. Use when you need the complete fundamental picture vs. one metric (for one metric use edgar_company_concept). Leads with latest_annual — revenue, net income, assets, cash, EPS for the most recent fiscal year, resolved to whichever XBRL concept the filer currently reports under — and flags retired concepts (e.g. a pre-ASC-606 Revenues tag) as stale so a 2010 figure is never mistaken for current. Large payload; agents typically use this once to discover available concepts then narrow to edgar_company_concept for follow-up queries. For just the headline figures plus the recent filings list, edgar_company_snapshot is the smaller one-call answer.

Input Schema

TableJSON Schema

Name	Required	Description
`cik`	No	REQUIRED (or one of its aliases `ticker` / `ticker_or_cik`). Ticker ("NVDA") or CIK number ("320193"). Tickers are auto-resolved to CIKs internally.
`ticker`	No	Alias for `cik` — same thing, a ticker or a CIK. The spelling edgar_fund_holdings and edgar_ticker_to_cik use.
`ticker_or_cik`	No	Alias for `cik` — the spelling edgar_company_filings, edgar_insider_transactions and edgar_product_revenue use.

Output Schema

TableJSON Schema

Name	Required	Description
`cik`	Yes	Company CIK number
`year_note`	No	How `year` is derived
`company_name`	Yes	Official company name
`latest_annual`	Yes	Canonical line items for the most recent fiscal year — revenue, net_income, operating_income, gross_profit, total_assets, total_liabilities, stockholders_equity, cash_and_equivalents, eps_basic, eps_diluted, shares_outstanding, research_and_development — each resolved to whichever concept the filer currently reports under; null when the filer reports no current value
`key_financials`	Yes	Per-concept detail. Current concepts first, retired (stale) concepts last — a stale concept is kept because a historical series still needs it, never silently dropped
`stale_concepts`	Yes	Concepts the filer has stopped reporting; present in key_financials flagged stale, never used in latest_annual
`latest_period_end`	No	Period end of that most recent annual report (YYYY-MM-DD)
`available_concepts`	Yes	Total number of US-GAAP financial concepts available for this company
`latest_fiscal_year`	No	Fiscal year of the filer's most recent annual report across every concept examined

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 24, 2026

changedInput schema / properties / cik / description

Previous value: -"Ticker (\"NVDA\") or CIK number (\"320193\"). Tickers are auto-resolved to CIKs internally."New value: +"REQUIRED (or one of its aliases `ticker` / `ticker_or_cik`). Ticker (\"NVDA\") or CIK number (\"320193\"). Tickers are auto-resolved to CIKs internally."

addedInput schema / properties / ticker

Added value: +{
+  "description": "Alias for `cik` — same thing, a ticker or a CIK. The spelling edgar_fund_holdings and edgar_ticker_to_cik use.",
+  "type": "string"
+}

addedInput schema / properties / ticker_or_cik

Added value: +{
+  "description": "Alias for `cik` — the spelling edgar_company_filings, edgar_insider_transactions and edgar_product_revenue use.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "cik"
-]New value: +[]

Changed21 schema fields changedAug 28, 2026

changedOutput schema / properties / available_concepts / description

Previous value: -"Total number of available US-GAAP concepts"New value: +"Total number of US-GAAP financial concepts available for this company"

changedOutput schema / properties / key_financials / additionalProperties / properties / label / description
```
Previous value: -"Human-readable metric label"New value: +"Human-readable label for the XBRL concept"
```

addedOutput schema / properties / key_financials / additionalProperties / properties / most_recent_annual / description

Added value: +"Most recent annual (10-K/20-F/40-F) value, or null when the filer reports no annual value for this concept"

changedOutput schema / properties / key_financials / additionalProperties / properties / most_recent_annual / properties / filed / description
```
Previous value: -"Date filing was submitted"New value: +"Date the filing was submitted (YYYY-MM-DD)"
```

addedOutput schema / properties / key_financials / additionalProperties / properties / most_recent_annual / properties / form

Added value: +{
+  "description": "Annual-report form the value came from (10-K, 10-K/A, 20-F, 40-F)",
+  "type": "string"
+}

addedOutput schema / properties / key_financials / additionalProperties / properties / most_recent_annual / properties / period_end
```
Added value: +{
+  "description": "Period end / balance-sheet date (YYYY-MM-DD)",
+  "type": "string"
+}
```

added

Output schema / properties / key_financials / additionalProperties / properties / most_recent_annual / properties / period_start

Added value: +{
+  "description": "Period start (YYYY-MM-DD); present for duration concepts such as revenue, absent for balance-sheet instants",
+  "type": "string"
+}

addedOutput schema / properties / key_financials / additionalProperties / properties / most_recent_annual / properties / unit
```
Added value: +{
+  "description": "XBRL unit: USD, USD/shares, shares, or pure",
+  "type": "string"
+}
```
changedOutput schema / properties / key_financials / additionalProperties / properties / most_recent_annual / properties / value / description
```
Previous value: -"Metric value"New value: +"Metric value in `unit`"
```

changed

Output schema / properties / key_financials / additionalProperties / properties / most_recent_annual / properties / year / description

Previous value: -"Fiscal year"New value: +"Fiscal year the reporting period ENDS in, derived from period_end (NOT the SEC fy filing-year field, which stamps prior-year comparatives with the restating filing's year)"

addedOutput schema / properties / key_financials / additionalProperties / properties / most_recent_annual / required
```
Added value: +[
+  "year",
+  "value",
+  "filed",
+  "period_end",
+  "form",
+  "unit"
+]
```

addedOutput schema / properties / key_financials / additionalProperties / properties / stale

Added value: +{
+  "description": "true when this concept's latest annual period ends before the filer's latest annual report — the filer stopped reporting it (e.g. a pre-ASC-606 Revenues tag). Real history, not the current figure",
+  "type": "boolean"
+}

addedOutput schema / properties / key_financials / additionalProperties / properties / stale_note

Added value: +{
+  "description": "Present when stale: which fiscal year the concept stops at, what the filer's latest report covers, and which current concept in latest_annual replaces it",
+  "type": "string"
+}

addedOutput schema / properties / key_financials / additionalProperties / required
```
Added value: +[
+  "label",
+  "most_recent_annual",
+  "stale"
+]
```

changedOutput schema / properties / key_financials / description

Previous value: -"Key financial metrics with most recent annual values"New value: +"Per-concept detail. Current concepts first, retired (stale) concepts last — a stale concept is kept because a historical series still needs it, never silently dropped"

addedOutput schema / properties / latest_annual

Added value: +{
+  "additionalProperties": {
+    "description": "Most recent annual (10-K/20-F/40-F) value, or null when the filer reports no annual value for this concept",
+    "properties": {
+      "concept": {
+        "description": "The us-gaap concept this value was read from — the one the filer currently reports this line under",
+        "type": "string"
+      },
+      "filed": {
+        "description": "Date the filing was submitted (YYYY-MM-DD)",
+        "type": "string"
+      },
+      "form": {
+        "description": "Annual-report form the value came from (10-K, 10-K/A, 20-F, 40-F)",
+        "type": "string"
+      },
+      "period_end": {
+        "description": "Period end / balance-sheet date (YYYY-MM-DD)",
+        "type": "string"
+      },
+      "period_start": {
+        "description": "Period start (YYYY-MM-DD); present for duration concepts such as revenue, absent for balance-sheet instants",
+        "type": "string"
+      },
+      "unit": {
+        "description": "XBRL unit: USD, USD/shares, shares, or pure",
+        "type": "string"
+      },
+      "value": {
+        "description": "Metric value in `unit`",
+        "type": "number"
+      },
+      "year": {
+        "description": "Fiscal year the reporting period ENDS in, derived from period_end (NOT the SEC fy filing-year field, which stamps prior-year comparatives with the restating filing's year)",
+        "type": "number"
+      }
+    },
+    "required": [
+      "year",
+      "value",
+      "filed",
+      "period_end",
+      "form",
+      "unit",
+      "concept"
+    ],
+    "type": [
+      "object",
+      "null"
+    ]
+  },
+  "description": "Canonical line items for the most recent fiscal year — revenue, net_income, operating_income, gross_profit, total_assets, total_liabilities, stockholders_equity, cash_and_equivalents, eps_basic, eps_diluted, shares_outstanding, research_and_development — each resolved to whichever concept the filer currently reports under; null when the filer reports no current value",
+  "type": "object"
+}

addedOutput schema / properties / latest_fiscal_year

Added value: +{
+  "description": "Fiscal year of the filer's most recent annual report across every concept examined",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / latest_period_end

Added value: +{
+  "description": "Period end of that most recent annual report (YYYY-MM-DD)",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / stale_concepts

Added value: +{
+  "description": "Concepts the filer has stopped reporting; present in key_financials flagged stale, never used in latest_annual",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / year_note

Added value: +{
+  "description": "How `year` is derived",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "cik",
-  "company_name",
-  "key_financials",
-  "available_concepts"
-]New value: +[
+  "cik",
+  "company_name",
+  "latest_annual",
+  "key_financials",
+  "stale_concepts",
+  "available_concepts"
+]

Changed1 schema field changedJun 22, 2026

changedInput schema / properties / cik / description

Previous value: -"Company CIK number (e.g., \"320193\" for Apple). Use edgar_ticker_to_cik to look up if needed."New value: +"Ticker (\"NVDA\") or CIK number (\"320193\"). Tickers are auto-resolved to CIKs internally."

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "available_concepts": {
+      "description": "Total number of available US-GAAP concepts",
+      "type": "number"
+    },
+    "cik": {
+      "description": "Company CIK number",
+      "type": "string"
+    },
+    "company_name": {
+      "description": "Official company name",
+      "type": "string"
+    },
+    "key_financials": {
+      "additionalProperties": {
+        "properties": {
+          "label": {
+            "description": "Human-readable metric label",
+            "type": "string"
+          },
+          "most_recent_annual": {
+            "properties": {
+              "filed": {
+                "description": "Date filing was submitted",
+                "type": "string"
+              },
+              "value": {
+                "description": "Metric value",
+                "type": "number"
+              },
+              "year": {
+                "description": "Fiscal year",
+                "type": "number"
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "description": "Key financial metrics with most recent annual values",
+      "type": "object"
+    }
+  },
+  "required": [
+    "cik",
+    "company_name",
+    "key_financials",
+    "available_concepts"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "cik": "320193"
+  }
+]
```
First observedApr 22, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it flags retired concepts as stale, notes the payload is large, and explains that latest_annual is resolved to whichever XBRL concept the filer currently reports under. This is meaningful behavioral disclosure that helps the agent anticipate output quirks.

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?

The description is dense but well-organized: it front-loads the core purpose, then covers parameter semantics, output characteristics, usage guidance, and sibling routing. Every sentence earns its place, though it is somewhat long. The structure is logical and the key differentiators are prominent.

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 (hundreds of concepts, aliases, large payload, stale concept handling), the description is remarkably complete. It covers what the tool returns, how to call it, what the aliases are, when to use it vs. alternatives, and what to expect in terms of payload size and data quality. The output schema exists, so return values need not be detailed further. Nothing an agent needs to select and invoke this tool correctly is missing.

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 description coverage is 100%, so the schema already documents all three parameters. The description adds value by clarifying that `cik` is the primary argument, that tickers are auto-resolved to CIKs internally, and that `ticker`/`ticker_or_cik` are aliases. This goes beyond the schema's per-parameter descriptions by explaining the relationship between the three parameters and the resolution behavior.

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 states a specific verb ('Returns every reported financial metric'), a specific resource ('full XBRL fundamentals dump for a US public company'), and explicitly distinguishes itself from siblings (edgar_company_concept, edgar_company_snapshot). It clearly identifies the tool's scope and differentiates it from alternatives.

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?

The description provides explicit when-to-use guidance: 'Use when you need the complete fundamental picture vs. one metric (for one metric use edgar_company_concept)' and 'For just the headline figures plus the recent filings list, edgar_company_snapshot is the smaller one-call answer.' It also notes the typical usage pattern: 'agents typically use this once to discover available concepts then narrow to edgar_company_concept for follow-up queries.' This is explicit routing with alternatives.

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

All Edgar 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.