Skip to main content
Glama

Edgar

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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 (FY/Q1/Q2/Q3/Q4) and form, newest first, PLUS a latest field holding the single freshest data point. 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. 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. 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.

Input Schema

TableJSON 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".
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", or "Q4" (derived: FY minus Q1-Q3). Combine with fiscal_year for a single figure.
ticker_or_cikNoAlias for `cik` — the spelling used by edgar_company_filings, edgar_insider_transactions and edgar_product_revenue.

Output Schema

TableJSON 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. 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: +[]
  2. 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"
+}
  3. 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\"."
  4. 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"
+}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "cik": "320193",
+    "concept": "Revenue"
+  },
+  {
+    "cik": "1652044",
+    "concept": "NetIncomeLoss"
+  }
+]
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=true, idempotentHint=true), the description discloses important behaviors: Q4 rows are derived (FY minus Q1-Q3, marked derived:true), the `latest` field returns the newest 10-Q when fresher than the last 10-K, and results come back newest-first with fiscal_period and form labels. It also explains tag resolution (post-ASC-606) — all useful behavioral context not present in annotations.

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 but well-structured: it opens with the core purpose, then explains input semantics, then return behavior and usage examples. Some redundancy exists (e.g., mentioning annual/quarterly return in both the purpose and the behavior sections), but for a complex tool with many nuances the length is justified. It remains readable and front-loaded with the most critical info.

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 (8 parameters, aliases, derived data, period filtering), the description covers all essential operational details: how to specify the company and metric, what the returned structure contains, the meaning of `latest`, and when to use filters. With an output schema present, return-value documentation is covered, and the description fills the remaining behavioral and selection gaps comprehensively.

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 baseline is 3. The description adds value by explaining that `concept` takes friendly names that get resolved to XBRL tags, and that `cik` accepts ticker or CIK with aliases across sibling tools. It also clarifies the `fiscal_year` filtering is based on the filer's own fiscal calendar. This goes slightly beyond the schema's per-parameter descriptions.

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 and resource: "AUTHORITATIVE historical financials for any US public company." It clearly explains what the tool does (retrieves SEC XBRL filings, resolves metric names, returns annual/quarterly values) and even distinguishes itself by emphasizing official SEC data over "third-party scrapes." This is more than enough to differentiate from sibling tools like edgar_company_filings or edgar_company_facts.

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 gives explicit usage scenarios: "Use for 'what was AAPL's revenue in 2024', 'NVDA's latest cash position', 'show me long-term debt trend'..." It also provides when-not guidance, such as "do not default to `latest` for a period question" and explains when to use `annual` vs the default. The alias explanations referencing sibling tools (edgar_fund_holdings, edgar_company_filings) further disambiguate usage.

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

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

Resources