Skip to main content
Glama

Edgar Filing Documents

edgar_filing_documents
Read-onlyIdempotent

AUTHORITATIVE list of the SEC filing documents inside ONE specific filing, by accession number. Retrieve a filing / its contents / attachments: pass the accession (e.g. "0000320193-25-000079", with or without dashes) plus the filer's ticker ("AAPL") or CIK ("320193"). Returns every document in the filing folder — the primary document (10-K / 10-Q / 8-K body), all exhibits, and XBRL files — each with name, type, size, and a direct https URL, plus the filing's form type, filing date, and human -index.html page. Set include_primary_text:true to also pull the primary document's text (HTML stripped to plaintext, ~40k chars). Use to list a 10-K / 10-Q / 8-K's exhibits, retrieve filing contents/attachments, or fetch the text of a filing. You can pass an exact accession, OR just a ticker + form_type to auto-resolve the latest matching filing (no accession lookup needed). Examples: edgar_filing_documents({ticker: "NVDA", form_type: "10-K"}) for the documents in NVIDIA's latest annual report; edgar_filing_documents({accession: "0000320193-25-000079", ticker: "AAPL", include_primary_text: true}) for a specific filing's text.

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": {
      "ticker": "AAPL",
      "form_type": "10-K",
      "include_primary_text": true
    },
    "name": "edgar_filing_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoThe filer's CIK number (e.g. "320193"). Provide this OR ticker.
filedNoOnly consider filings filed on this date, in this month, or in this year — "2026-09-29", "2026-09", "2026" (US spellings "09/29/2026" and "September 29, 2026" accepted). **Pass this whenever the question names a date** ("Tesla's September 29 2026 8-K"): without it the NEWEST filing of that form is used, and for an 8-K that is routinely a different filing.
tickerNoThe filer's ticker (e.g. "AAPL", "NVDA") or company name. Provide this OR cik. Tickers are auto-resolved to CIKs.
accessionNoOptional SEC accession number of a specific filing, with or without dashes (e.g. "0000320193-25-000079"). Omit it to auto-resolve the latest filing — pass form_type instead, and the response will say `accession_source:"auto_selected"` and list under `auto_selected.candidates` the other filings you might have meant. If the question names WHICH filing (a date, "the September 29 8-K"), pass `filed` or the accession rather than relying on that choice.
form_typeNoWhen accession is omitted, the form type of the latest filing to fetch, e.g. "10-K", "10-Q", "8-K", "DEF 14A" — or a `|`-separated SET ("10-K|10-Q") for "the most recent of either, whichever is newer". Omit both accession and form_type to get the single most recent filing of ANY type at all (routine 8-Ks/Form 4s/Form 144s included, not just annual/quarterly reports) — use the `|` set instead when you specifically want the newest 10-K or 10-Q.
filing_dateNoAlias for `filed`.
ticker_or_cikNoAlias for `ticker` / `cik` — the single-argument spelling edgar_company_filings and edgar_insider_transactions use. Takes either a ticker or a CIK.
include_primary_textNoWhen true, also fetch the primary document and return its text (HTML stripped to plaintext, truncated to ~40,000 chars). Default false. For the FULL, pageable document text — or just one section like going-concern/liquidity — use edgar_filing_text instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / accession / description
      Previous value: -"Optional SEC accession number of a specific filing, with or without dashes (e.g. \"0000320193-25-000079\"). Omit it to auto-resolve the latest filing — pass form_type instead."New value: +"Optional SEC accession number of a specific filing, with or without dashes (e.g. \"0000320193-25-000079\"). Omit it to auto-resolve the latest filing — pass form_type instead, and the response will say `accession_source:\"auto_selected\"` and list under `auto_selected.candidates` the other filings you might have meant. If the question names WHICH filing (a date, \"the September 29 8-K\"), pass `filed` or the accession rather than relying on that choice."
    • addedInput schema / properties / filed
      Added value: +{
      +  "description": "Only consider filings filed on this date, in this month, or in this year — \"2026-09-29\", \"2026-09\", \"2026\" (US spellings \"09/29/2026\" and \"September 29, 2026\" accepted). **Pass this whenever the question names a date** (\"Tesla's September 29 2026 8-K\"): without it the NEWEST filing of that form is used, and for an 8-K that is routinely a different filing.",
      +  "type": "string"
      +}
    • addedInput schema / properties / filing_date
      Added value: +{
      +  "description": "Alias for `filed`.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / form_type / description
      Previous value: -"When accession is omitted, the form type of the latest filing to fetch, e.g. \"10-K\", \"10-Q\", \"8-K\", \"DEF 14A\". Omit both accession and form_type to get the single most recent filing of any type."New value: +"When accession is omitted, the form type of the latest filing to fetch, e.g. \"10-K\", \"10-Q\", \"8-K\", \"DEF 14A\" — or a `|`-separated SET (\"10-K|10-Q\") for \"the most recent of either, whichever is newer\". Omit both accession and form_type to get the single most recent filing of ANY type at all (routine 8-Ks/Form 4s/Form 144s included, not just annual/quarterly reports) — use the `|` set instead when you specifically want the newest 10-K or 10-Q."
  3. Changed1 schema field changed
    • addedInput schema / properties / ticker_or_cik
      Added value: +{
      +  "description": "Alias for `ticker` / `cik` — the single-argument spelling edgar_company_filings and edgar_insider_transactions use. Takes either a ticker or a CIK.",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "form_type": "10-K",
      +    "include_primary_text": true,
      +    "ticker": "AAPL"
      +  },
      +  {
      +    "accession": "0000320193-25-000079",
      +    "ticker": "AAPL"
      +  }
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / include_primary_text / description
      Previous value: -"When true, also fetch the primary document and return its text (HTML stripped to plaintext, truncated to ~40,000 chars). Default false."New value: +"When true, also fetch the primary document and return its text (HTML stripped to plaintext, truncated to ~40,000 chars). Default false. For the FULL, pageable document text — or just one section like going-concern/liquidity — use edgar_filing_text instead."
  6. Changed4 schema fields changed
    • changedInput schema / properties / accession / description
      Previous value: -"SEC accession number of the filing, with or without dashes (e.g. \"0000320193-25-000079\" or \"000032019325000079\"). 18 digits shaped 10-2-6."New value: +"Optional SEC accession number of a specific filing, with or without dashes (e.g. \"0000320193-25-000079\"). Omit it to auto-resolve the latest filing — pass form_type instead."
    • addedInput schema / properties / form_type
      Added value: +{
      +  "description": "When accession is omitted, the form type of the latest filing to fetch, e.g. \"10-K\", \"10-Q\", \"8-K\", \"DEF 14A\". Omit both accession and form_type to get the single most recent filing of any type.",
      +  "type": "string"
      +}
    • changedInput schema / properties / ticker / description
      Previous value: -"The filer's ticker (e.g. \"AAPL\") or company name. Provide this OR cik — needed to build the filing archive path. Tickers are auto-resolved to CIKs."New value: +"The filer's ticker (e.g. \"AAPL\", \"NVDA\") or company name. Provide this OR cik. Tickers are auto-resolved to CIKs."
    • changedInput schema / required
      Previous value: -[
      -  "accession"
      -]New value: +[]
  7. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive safety, so the description correctly spends its words on behavior: return contents (every document with name, type, size, https URL, form type, filing date, index page), the ~40k char truncation on primary text, and the `accession_source:"auto_selected"` fallback with candidate alternatives. It stops short of describing pagination or size caps on large filings, which is the main residual gap.

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?

Front-loaded with the identity of the tool, then scope, then return shape, then the alternative tool, then examples — a sensible order. It is on the long side and the two worked examples partly repeat points already made in the body, costing some economy.

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 an 8-parameter, zero-required, no-output-schema tool, the description carries the necessary burden: what comes back, what the optional flag adds, what happens when accession is omitted, and where to go for the fuller text. Coverage is sufficient for an agent to call it correctly without opening 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 the baseline is 3. The description does add the meaningful OR-relationship (exact accession vs. ticker + form_type auto-resolve) and the primary-text truncation behavior, but most parameter detail it gives is already spelled out in the schema fields, and the alias parameters (filing_date, ticker_or_cik) are never mentioned.

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?

States a specific verb and resource — list the SEC filing documents inside ONE specific filing — with a clear scope ('by accession number') and an uppercase AUTHORITATIVE qualifier that signals trust level. It distinguishes itself from edgar_filing_text and edgar_filing_exhibit_text by naming them as the alternative for full/section text.

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?

Explicitly enumerates when to use it (list exhibits, retrieve contents/attachments, fetch filing text via include_primary_text) and routes elsewhere for the full pageable text ('use edgar_filing_text instead'). It also warns when NOT to rely on auto-resolution by pointing at `filed` for date-specific questions.

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.