edgar-search-mcp

Overview Schema Source Related Servers Discussions Admin

list_filing_documents

Read-only

Lists the documents in an SEC EDGAR filing index from any filing file URL, including the main document, exhibits, and data files with type, size, sequence, and link.

Instructions

The rows of one filing's index page: the main document, its exhibits and its data files.

url is any file URL of the filing, as returned by list_filings or search_filings. Each row has sequence, description, type and size as the index page shows them, the file name (document) and its url. This is a view read from the page's HTML table by the rules named in transformation; the page itself is original.url, which get_filing_document returns byte for byte. A row with a link the rules do not read is left out and listed in skipped_rows and warnings. The type is the SEC's label for a document ("8-K", "EX-99.1", "GRAPHIC", ...); it does not say whether a document was filed or furnished.

Input Schema

Name	Required	Description	Default
`url`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Oct 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "envelope": {
+      "properties": {
+        "contract_version": {
+          "const": "1.0"
+        },
+        "representation": {
+          "enum": [
+            "source",
+            "source_records",
+            "parsed_source",
+            "transformed"
+          ]
+        },
+        "returned_at": {
+          "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}Z$",
+          "type": "string"
+        },
+        "sources": {
+          "items": {
+            "$ref": "#/$defs/source"
+          },
+          "minItems": 1,
+          "type": "array"
+        },
+        "unresolved": {
+          "items": {
+            "$ref": "#/$defs/unresolved"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "contract_version",
+        "representation",
+        "sources",
+        "returned_at"
+      ],
+      "type": "object"
+    },
+    "source": {
+      "properties": {
+        "cache_hit": {
+          "type": "boolean"
+        },
+        "frozen": {
+          "type": "boolean"
+        },
+        "retrieved_at": {
+          "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}Z$",
+          "type": "string"
+        },
+        "sha256": {
+          "pattern": "^[0-9a-f]{64}$",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "url": {
+          "pattern": "^https://(www|data|efts)\\.sec\\.gov/",
+          "type": "string"
+        }
+      },
+      "required": [
+        "url",
+        "retrieved_at",
+        "frozen",
+        "cache_hit"
+      ],
+      "type": "object"
+    },
+    "unresolved": {
+      "properties": {
+        "reason": {
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "reason"
+      ],
+      "type": "object"
+    }
+  },
+  "$id": "edgar://contract/1.0/list_filing_documents",
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "allOf": [
+    {
+      "$ref": "#/$defs/envelope"
+    },
+    {
+      "properties": {
+        "documents": {
+          "items": {
+            "required": [
+              "sequence",
+              "description",
+              "type",
+              "size",
+              "document",
+              "url"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "original": {
+          "required": [
+            "url",
+            "sha256",
+            "tool"
+          ],
+          "type": "object"
+        },
+        "representation": {
+          "const": "transformed"
+        },
+        "skipped_rows": {
+          "items": {
+            "required": [
+              "line",
+              "cells",
+              "links",
+              "reason"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "transformation": {
+          "required": [
+            "name",
+            "rules"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "cik",
+        "accession_number",
+        "transformation",
+        "original",
+        "documents",
+        "skipped_rows",
+        "warnings"
+      ]
+    }
+  ],
+  "type": "object"
+}

First observedv0.1.0Oct 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With readOnlyHint/openWorldHint already covering the safety profile, the description goes well beyond: it discloses that results are parsed from the page's HTML table by the rules in `transformation`, that unparseable links are omitted and surfaced in `skipped_rows` and `warnings`, and that the type label is SEC's own ('8-K', 'EX-99.1', 'GRAPHIC') without indicating filed vs furnished. Those are non-obvious caveats an agent needs before trusting the output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the return shape in the first sentence, then covers input, row fields, provenance, and caveats in a tight sequence. Every clause adds information; nothing is filler.

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?

Output schema exists, yet the description still names the per-row fields (sequence, description, type, size, document, url) and the auxiliary outputs (skipped_rows, warnings), and points at get_filing_document for the raw page. For a single-parameter read tool, nothing material is missing.

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 0% — the single `url` property has no description at all — so the description has to carry it, and it does: 'any file URL of the filing' plus the note that such URLs come from list_filings or search_filings. It still doesn't clarify whether query strings/fragments or non-primary documents are accepted, keeping it off a 5.

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?

Names the exact resource — the rows of one filing's index page — and enumerates what those rows contain (main document, exhibits, data files). That distinguishes it cleanly from list_filings (the list of filings) and get_filing_document (raw page bytes), so an agent can pick it without opening the schema.

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?

Gives a concrete entry condition by tying the url parameter to 'as returned by list_filings or search_filings', which tells the agent which sibling produces the input. It also implicitly separates this tool from get_filing_document by saying that tool returns the page byte for byte. No explicit exclusions or when-not-to-use statement, so not a 5.

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

Deploy Server