Skip to main content
Glama

Edgar

by io.github.pipeworx-io

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". Omit both accession and form_type to get the single most recent filing of any type.
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. Dates show when Glama detected each change.

  1. 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"
+  }
+]
  2. 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."
  3. 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: +[]
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is established. The description adds behavioral context: it returns 'every document in the filing folder' with specific fields, truncates primary text to ~40k chars, and auto-resolves ticker to CIK. No contradictions with 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 moderately long but well-organized: starts with core purpose, then parameter explanations, then examples. Every sentence adds value. However, it could be slightly more compact by merging some details (e.g., examples are repeated). Still, it is efficient for the amount of information conveyed.

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 has 5 optional parameters, no output schema, and multiple use cases, the description covers all needed context: what is returned (documents with details, form type, date, index page), the two invocation modes, primary text option and its limitation, and the alternative for full text. No gaps remain.

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 has 5 parameters, all with descriptions (100% coverage). The description adds value beyond schema by providing examples, explaining auto-resolution of ticker, clarifying default for include_primary_text, and directing to edgar_filing_text for full text. This extra guidance improves usability.

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 clearly states the tool retrieves documents from a single SEC filing by accession number, listing them with details. It distinguishes from sibling tools like edgar_filing_text (for full text) and edgar_company_filings (for list of filings). Examples show both usage modes (by accession or ticker+form_type), providing specific verb+resource.

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?

The description specifies when to use: 'Use to list a 10-K / 10-Q / 8-K's exhibits, retrieve filing contents/attachments, or fetch the text of a filing.' It also explicitly suggests an alternative: 'For the FULL, pageable document text... use edgar_filing_text instead.' While not exhaustive about exclusions, this covers key decision points.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose, with detailed descriptions that prevent confusion. Overlapping tools like ask_pipeworx vs ask_pipeworx_grounded are explicitly differentiated by use case (casual vs high-stakes) and refusal behavior.

Naming Consistency4/5

Names are mostly consistent using lowercase underscores, but there is a mix of verb-initial (ask_pipeworx, generate_llms_txt) and noun-initial (edgar_company_facts, polymarket_arbitrage) patterns, which slightly reduces predictability.

Tool Count3/5

37 tools is high, but the server covers a broad domain of authoritative data sources (SEC, FDA, FRED, prediction markets, etc.). While it exceeds the typical 15-tool threshold, each tool serves a distinct data need and the count feels justified for the scope.

Completeness5/5

The tool surface covers the full lifecycle of data retrieval and analysis: discovery (discover_tools), single queries (ask_pipeworx), grounded lookups (ask_pipeworx_grounded), multi-source research (deep_research), entity profiles, comparisons, historical data, and subscription monitoring. No major gaps are evident.

Resources