edgar-mcp

Overview Schema Source Related Servers Discussions Admin

list_filings

Retrieve a company's SEC filings newest first, with amendments flagged. Filter by form type and date range to locate filing details or accession numbers.

Instructions

List a company's SEC filings, newest first, with amendments flagged.

Use this to find out what a company filed and when, to get an accession number for get_filing_section, or to check whether a company files at all.

Form types have variants that all mean "annual report": 10-K is the normal one, 10-K/A is an amendment to a previously filed one, and 10-KT is a transition report covering a short year after the company changed its fiscal calendar. Asking for form "10-K" returns all of these. A foreign private issuer files 20-F or 40-F instead and will have no 10-K at all — if a company you expect to see has no annual report, ask for form "20-F".

Amendments matter for accuracy. When a 10-K/A exists, the original 10-K is marked superseded: true with superseded_by pointing at the amendment. A figure taken from a superseded filing may have been revised. Prefer the amendment, and say which filing you used.

The response also reports fiscal_year_end as MM-DD. Read it before comparing this company's fiscal year with another company's.

Args: cik: The company's CIK, from resolve_company. Zero padding optional. form: Filter to a form type, e.g. "10-K", "10-Q", "8-K", "20-F". Amendment and transition variants are included automatically. since: Only filings filed on or after this date, as YYYY-MM-DD. until: Only filings filed on or before this date, as YYYY-MM-DD. limit: Maximum filings to return. Default 20.

Returns: company, cik, fiscal_year_end, and a filings list. Each filing carries form, base_form, is_amendment, filing_date, period_of_report, accession_number, superseded flags, and URLs to the document and index.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cik`	Yes
`form`	No
`limit`	No
`since`	No
`until`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations present, the description fully covers behavioral traits: sorted newest first, amendment and transition variants included, superseded flag semantics, and fiscal_year_end format. It even warns about the accuracy risk of superseded filings, which is exactly the kind of context an agent needs.

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?

The description is detailed but every section earns its place: summary, usage, form variants, amendment handling, return format, Args, and Returns. It is front-loaded with the core purpose and organized so an agent can quickly extract the key facts.

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 five parameters, no annotations, and an output schema, the description is fully complete. It explains return fields, filtering behavior, edge cases like transition reports and foreign private issuers, and the relationship to sibling tools. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries full responsibility for parameter meaning. It explains all five parameters: cik source, form variant inclusion, since/until date format, and limit default. This compensates completely for the schema's lack of 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 opening sentence states a specific verb and resource ('List a company's SEC filings, newest first, with amendments flagged') and clearly differentiates the tool from siblings by showing how it feeds into get_filing_section. The purpose is unmistakable.

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 explicitly says when to use the tool: to find filing dates, get an accession number for get_filing_section, or check whether a company files at all. It also gives practical guidance on form-type variants and when to try 20-F/40-F instead of 10-K, which steers the agent toward correct usage.

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

Deploy Server