Skip to main content
Glama

Edgar Company Concept

edgar_company_concept
Read-onlyIdempotent

AUTHORITATIVE historical financials for any US public company. Source: SEC XBRL filings (the official numbers companies file, not third-party scrapes). Send the company as cik — that argument takes a TICKER ("AAPL") or a CIK ("320193"), and ticker / ticker_or_cik are accepted as aliases for it — plus the metric as concept (alias metric), which takes a friendly name: Revenue, NetIncomeLoss, Cash, LongTermDebt, EarningsPerShareDiluted. The tool resolves the right XBRL tag for that filer (post-ASC-606 companies use RevenueFromContractWithCustomerExcludingAssessedTax instead of "Revenues", etc.). Returns both ANNUAL (10-K) and QUARTERLY (10-Q) values by default, each labeled with fiscal_period and form, newest first, PLUS a latest field holding the single freshest data point. Every row also carries period_start/period_end/duration_days so the window a value covers is never ambiguous. Q4 rows are DERIVED (FY minus Q1-Q3, marked derived:true) because SEC filers never report a standalone Q4 fact — so "revenue Q4 2024" questions are answerable directly from values. CASH-FLOW-STATEMENT concepts (OperatingCashFlow, Capex and siblings) are filed CUMULATIVELY by most filers — a 10-Q's six-month figure is reported under the SAME period label the discrete quarter would use. Those rows are labeled fiscal_period "H1" (six months) or "9M" (nine months) with ytd:true, never "Q2"/"Q3" bare, and a discrete-quarter sibling (derived:true, e.g. Q2 = H1 minus Q1) is added alongside so "capex Q2" is still answerable without presenting the six-month total as a quarter. Income-statement lines (Revenue, NetIncomeLoss) are usually filed quarter-only already and are unaffected. For one specific period, pass fiscal_year and/or fiscal_period as ARGUMENTS and the values array comes back filtered to it (they are also the names of the fields on each returned row, which is what to match on if you ask for every period instead); do not default to latest for a period question. Use latest for point-in-time metrics like cash, runway, and debt — it is the newest 10-Q when one is more recent than the last 10-K, so a stale annual figure never masks a newer quarter; for a YTD-shaped concept, latest prefers the discrete derived quarter over the as-filed cumulative figure, so it is never silently a 2-3x-too-large number. Use for "what was AAPL's revenue in 2024", "NVDA's latest cash position", "show me long-term debt trend", anything where you need the SEC-filed number rather than an estimate.

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": {
      "cik": "320193",
      "concept": "Revenue"
    },
    "name": "edgar_company_concept"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoREQUIRED (or one of its aliases `ticker` / `ticker_or_cik`). Ticker (e.g., "AAPL") or CIK number (e.g., "320193"). Tickers are auto-resolved.
metricNoAlias for `concept` — the word this tool's own description uses for the thing you are asking about.
periodNoWhich reporting periods to return: "all" (default — annual 10-K + quarterly 10-Q), "annual" (10-K/20-F/40-F only), or "quarterly" (10-Q only). Point-in-time metrics (cash/runway/debt) usually want the default so the freshest quarter is included; use "annual" for clean year-over-year trends.
tickerNoAlias for `cik` — same thing, a ticker or a CIK. Declared because sibling SEC tools name this argument differently (edgar_fund_holdings uses `ticker`, edgar_company_filings uses `ticker_or_cik`) and a caller filling arguments from prose reaches for whichever it read; all three spellings work here.
conceptNoREQUIRED (alias `metric`). Metric name. Common: "Revenue" / "Revenues", "NetIncomeLoss", "Cash", "Assets", "Liabilities", "StockholdersEquity", "EarningsPerShareDiluted", "LongTermDebt", "SharesOutstanding" (newest cover-page count, dei), "Capex", "OperatingCashFlow", "ResearchAndDevelopment", "SGA", "CostOfRevenue", "DilutedShares", "PublicFloat". Exact us-gaap or dei tag names also work.
fiscal_yearNoOptional filter: return only rows for this fiscal year, e.g. "2024". This is the filer's OWN fiscal year label (NVDA's FY2024 ended Jan 2024), not a calendar year. Unmatched years are reported with the years that ARE available rather than as an empty result.
fiscal_periodNoOptional filter: return only rows for this period within the fiscal year — "FY" (annual), "Q1", "Q2", "Q3", "Q4" (derived: FY minus Q1-Q3), "H1" (six-month year-to-date, cash-flow-statement concepts only), or "9M" (nine-month year-to-date). Combine with fiscal_year for a single figure. Asking for "Q2"/"Q3" on a concept this filer reports cumulatively returns the DERIVED discrete quarter, not the H1/9M total.
ticker_or_cikNoAlias for `cik` — the spelling used by edgar_company_filings, edgar_insider_transactions and edgar_product_revenue.

Output Schema

NameRequiredDescriptionDefault
cikYesCompany CIK number
labelYesHuman-readable concept label
conceptYesUS-GAAP concept tag name
descriptionYesDetailed concept description
company_nameYesOfficial company name
annual_valuesYesAnnual values sorted by fiscal year descending

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / fiscal_period / description
      Previous value: -"Optional filter: return only rows for this period within the fiscal year — \"FY\" (annual), \"Q1\", \"Q2\", \"Q3\", or \"Q4\" (derived: FY minus Q1-Q3). Combine with fiscal_year for a single figure."New value: +"Optional filter: return only rows for this period within the fiscal year — \"FY\" (annual), \"Q1\", \"Q2\", \"Q3\", \"Q4\" (derived: FY minus Q1-Q3), \"H1\" (six-month year-to-date, cash-flow-statement concepts only), or \"9M\" (nine-month year-to-date). Combine with fiscal_year for a single figure. Asking for \"Q2\"/\"Q3\" on a concept this filer reports cumulatively returns the DERIVED discrete quarter, not the H1/9M total."
    • changedInput schema / properties / fiscal_period / enum
      Previous value: -[
      -  "FY",
      -  "Q1",
      -  "Q2",
      -  "Q3",
      -  "Q4"
      -]New value: +[
      +  "FY",
      +  "Q1",
      +  "Q2",
      +  "Q3",
      +  "Q4",
      +  "H1",
      +  "9M"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / concept / description
      Previous value: -"REQUIRED (alias `metric`). Metric name. Common: \"Revenue\" / \"Revenues\", \"NetIncomeLoss\", \"Cash\", \"Assets\", \"Liabilities\", \"StockholdersEquity\", \"EarningsPerShareDiluted\", \"LongTermDebt\"."New value: +"REQUIRED (alias `metric`). Metric name. Common: \"Revenue\" / \"Revenues\", \"NetIncomeLoss\", \"Cash\", \"Assets\", \"Liabilities\", \"StockholdersEquity\", \"EarningsPerShareDiluted\", \"LongTermDebt\", \"SharesOutstanding\" (newest cover-page count, dei), \"Capex\", \"OperatingCashFlow\", \"ResearchAndDevelopment\", \"SGA\", \"CostOfRevenue\", \"DilutedShares\", \"PublicFloat\". Exact us-gaap or dei tag names also work."
  3. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "cik": "320193",
      -    "concept": "Revenue"
      -  },
      -  {
      -    "cik": "1652044",
      -    "concept": "NetIncomeLoss"
      -  },
      -  {
      -    "cik": "DOV",
      -    "concept": "NetIncomeLoss",
      -    "fiscal_period": "FY",
      -    "fiscal_year": "2024",
      -    "period": "annual"
      -  }
      -]New value: +[
      +  {
      +    "cik": "320193",
      +    "concept": "Revenue"
      +  },
      +  {
      +    "cik": "1652044",
      +    "concept": "NetIncomeLoss"
      +  },
      +  {
      +    "cik": "DOV",
      +    "concept": "NetIncomeLoss",
      +    "fiscal_period": "FY",
      +    "fiscal_year": "2024",
      +    "period": "annual"
      +  },
      +  {
      +    "cik": "CAPR",
      +    "concept": "Cash"
      +  }
      +]
  4. Changed9 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "cik": "320193",
      -    "concept": "Revenue"
      -  },
      -  {
      -    "cik": "1652044",
      -    "concept": "NetIncomeLoss"
      -  }
      -]New value: +[
      +  {
      +    "cik": "320193",
      +    "concept": "Revenue"
      +  },
      +  {
      +    "cik": "1652044",
      +    "concept": "NetIncomeLoss"
      +  },
      +  {
      +    "cik": "DOV",
      +    "concept": "NetIncomeLoss",
      +    "fiscal_period": "FY",
      +    "fiscal_year": "2024",
      +    "period": "annual"
      +  }
      +]
    • changedInput schema / properties / cik / description
      Previous value: -"Ticker (e.g., \"AAPL\") or CIK number (e.g., \"320193\"). Tickers are auto-resolved."New value: +"REQUIRED (or one of its aliases `ticker` / `ticker_or_cik`). Ticker (e.g., \"AAPL\") or CIK number (e.g., \"320193\"). Tickers are auto-resolved."
    • changedInput schema / properties / concept / description
      Previous value: -"Metric name. Common: \"Revenue\" / \"Revenues\", \"NetIncomeLoss\", \"Cash\", \"Assets\", \"Liabilities\", \"StockholdersEquity\", \"EarningsPerShareDiluted\", \"LongTermDebt\"."New value: +"REQUIRED (alias `metric`). Metric name. Common: \"Revenue\" / \"Revenues\", \"NetIncomeLoss\", \"Cash\", \"Assets\", \"Liabilities\", \"StockholdersEquity\", \"EarningsPerShareDiluted\", \"LongTermDebt\"."
    • addedInput schema / properties / fiscal_period
      Added value: +{
      +  "description": "Optional filter: return only rows for this period within the fiscal year — \"FY\" (annual), \"Q1\", \"Q2\", \"Q3\", or \"Q4\" (derived: FY minus Q1-Q3). Combine with fiscal_year for a single figure.",
      +  "enum": [
      +    "FY",
      +    "Q1",
      +    "Q2",
      +    "Q3",
      +    "Q4"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / fiscal_year
      Added value: +{
      +  "description": "Optional filter: return only rows for this fiscal year, e.g. \"2024\". This is the filer's OWN fiscal year label (NVDA's FY2024 ended Jan 2024), not a calendar year. Unmatched years are reported with the years that ARE available rather than as an empty result.",
      +  "type": "string"
      +}
    • addedInput schema / properties / metric
      Added value: +{
      +  "description": "Alias for `concept` — the word this tool's own description uses for the thing you are asking about.",
      +  "type": "string"
      +}
    • addedInput schema / properties / ticker
      Added value: +{
      +  "description": "Alias for `cik` — same thing, a ticker or a CIK. Declared because sibling SEC tools name this argument differently (edgar_fund_holdings uses `ticker`, edgar_company_filings uses `ticker_or_cik`) and a caller filling arguments from prose reaches for whichever it read; all three spellings work here.",
      +  "type": "string"
      +}
    • addedInput schema / properties / ticker_or_cik
      Added value: +{
      +  "description": "Alias for `cik` — the spelling used by edgar_company_filings, edgar_insider_transactions and edgar_product_revenue.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "cik",
      -  "concept"
      -]New value: +[]
  5. Changed1 schema field changed
    • addedInput schema / properties / period
      Added value: +{
      +  "description": "Which reporting periods to return: \"all\" (default — annual 10-K + quarterly 10-Q), \"annual\" (10-K/20-F/40-F only), or \"quarterly\" (10-Q only). Point-in-time metrics (cash/runway/debt) usually want the default so the freshest quarter is included; use \"annual\" for clean year-over-year trends.",
      +  "enum": [
      +    "all",
      +    "annual",
      +    "quarterly"
      +  ],
      +  "type": "string"
      +}
  6. Changed2 schema fields changed
    • changedInput schema / properties / cik / description
      Previous value: -"Company CIK number (e.g., \"320193\" for Apple)"New value: +"Ticker (e.g., \"AAPL\") or CIK number (e.g., \"320193\"). Tickers are auto-resolved."
    • changedInput schema / properties / concept / description
      Previous value: -"US-GAAP concept name (e.g., \"Revenue\", \"NetIncomeLoss\", \"Assets\", \"Liabilities\", \"StockholdersEquity\", \"EarningsPerShareDiluted\")"New value: +"Metric name. Common: \"Revenue\" / \"Revenues\", \"NetIncomeLoss\", \"Cash\", \"Assets\", \"Liabilities\", \"StockholdersEquity\", \"EarningsPerShareDiluted\", \"LongTermDebt\"."
  7. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "annual_values": {
      +      "description": "Annual values sorted by fiscal year descending",
      +      "items": {
      +        "properties": {
      +          "filed": {
      +            "description": "Date filing was submitted",
      +            "type": "string"
      +          },
      +          "fiscal_year": {
      +            "description": "Fiscal year",
      +            "type": "number"
      +          },
      +          "period_end": {
      +            "description": "Period end date in YYYY-MM-DD format",
      +            "type": "string"
      +          },
      +          "unit": {
      +            "description": "Unit of measurement (e.g., USD, shares)",
      +            "type": "string"
      +          },
      +          "value": {
      +            "description": "Reported value",
      +            "type": "number"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "cik": {
      +      "description": "Company CIK number",
      +      "type": "string"
      +    },
      +    "company_name": {
      +      "description": "Official company name",
      +      "type": "string"
      +    },
      +    "concept": {
      +      "description": "US-GAAP concept tag name",
      +      "type": "string"
      +    },
      +    "description": {
      +      "description": "Detailed concept description",
      +      "type": "string"
      +    },
      +    "label": {
      +      "description": "Human-readable concept label",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "cik",
      +    "company_name",
      +    "concept",
      +    "label",
      +    "description",
      +    "annual_values"
      +  ],
      +  "type": "object"
      +}
  8. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "cik": "320193",
      +    "concept": "Revenue"
      +  },
      +  {
      +    "cik": "1652044",
      +    "concept": "NetIncomeLoss"
      +  }
      +]
  9. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, non-destructive, and open-world, but the description adds substantial behavioral context beyond those hints: SEC XBRL as source, annual and quarterly return shape, `latest` preference, derived Q4 rows, and YTD cash-flow handling. These details materially help an agent interpret and trust the results without contradicting any annotation.

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 long and dense, but it is front-loaded with the core purpose and source, then proceeds through important edge cases in a mostly logical order. Some parenthetical explanations and alias repetitions could be trimmed, but most sentences carry substantive guidance 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 complex multi-parameter schema, output schema presence, and annotations, the description is highly complete: it explains return structure, `latest`, derived Q4, YTD cash-flow labeling, filtering behavior, and alias acceptance. An agent has enough information to invoke it correctly for both period-specific and point-in-time questions.

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%, so the baseline is 3, but the description adds useful meaning beyond the schema: it explains the `cik`/`ticker`/`ticker_or_cik` aliasing, friendly vs exact concept names, XBRL tag resolution, and how `fiscal_year`/`fiscal_period` filtering interacts with returned rows. This is meaningful added semantics even though the schema already documents each parameter.

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 clearly states that this returns authoritative historical financials for US public companies from SEC XBRL filings, and names the core resource (metrics like Revenue, NetIncomeLoss, Cash). It does not explicitly distinguish itself from close siblings such as edgar_company_facts or edgar_xbrl_frames, so the purpose is clear but sibling differentiation is incomplete.

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 concrete usage guidance: use `latest` for point-in-time metrics, do not default to `latest` for period-specific questions, use `period: annual` for clean year-over-year trends, and filter by `fiscal_year`/`fiscal_period` for a single period. It stops short of naming when to choose a sibling tool like edgar_xbrl_frames instead, so it is clear context without explicit alternatives.

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.