Skip to main content
Glama

Edgar

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikNoThe filer's CIK number (e.g. "320193"). Provide this OR ticker.
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.
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.
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. 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."
  2. 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"
+}
  3. 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"
+  }
+]
  4. 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."
  5. 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: +[]
  6. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, read-only, open-world read, so the safety burden is covered. The description adds genuine behavioral context beyond that: what the return contains (name/type/size/direct https URL plus form type, filing date, index page), the ~40k-char truncation of include_primary_text, and the fallback-to-latest-any-type behavior. Not exhaustive on error cases, but well above what annotations supply.

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 purpose is front-loaded in the first sentence and every subsequent sentence carries usage or return information. It runs long and duplicates some of the schema's own examples, which is the only waste, but it stays readable and non-repetitive at the sentence level.

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?

With no output schema, the description carries the return-value burden and does so fully: enumerates documents, their metadata, and the filing-level fields. Combined with the annotations and 100%-covered schema, an agent has everything needed to call this correctly across both invocation modes.

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 and the schema already documents each field. The description still adds value by pairing parameters into real call shapes (accession+ticker, ticker+form_type), noting accession works with or without dashes, and clarifying the ticker/CIK OR and omitted-form_type semantics.

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+resource and scope: 'AUTHORITATIVE list of the SEC filing documents inside ONE specific filing, by accession number.' It explicitly distinguishes itself from the sibling it is not (edgar_filing_text for full pageable text, edgar_company_filings via the alias note), so an agent can separate it from siblings without opening a schema.

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?

Gives explicit when-to-use cases ('list a 10-K/10-Q/8-K's exhibits, retrieve filing contents/attachments, or fetch the text of a filing') and a clear alternative for full text ('use edgar_filing_text instead'). It also documents the auto-resolve path and even warns that omitting form_type returns routine 8-Ks/Form 4s, steering the agent to the `|` set when it wants a real report.

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