Equibles

List Filings

ListFilings

Read-only

List stored SEC filings and earnings-call transcripts newest first. Omit ticker for a market-wide feed or provide one ticker for a company-specific list. Returns company identity, document IDs, types, filing and reporting dates, SEC item numbers, line counts, EDGAR accession numbers and acceptance times (UTC; blank for filings stored before October 2026), and page totals. Supports date, document-type, and exact SEC item-number filters. Hidden document types remain excluded unless explicitly requested. When the deployment summarizes documents, each row adds a one- or two-sentence summary of what the document says, and when it has a public document viewer, each row adds the filing's page URL to share with the user. Pass a returned ID to SearchDocument or ReadDocumentLines.

Input Schema

Name	Required	Description
`page`	No	Page number for pagination (default: 1)
`ticker`	No	Optional company ticker symbol (e.g., AAPL, MSFT); a listing outside the US is MIC:TICKER (e.g. XPAR:AIR), whose list includes its ESEF reports. Omit for all companies.
`endDate`	No	Optional end date filter in YYYY-MM-DD format
`maxItems`	No	Maximum number of documents per page (default: 10)
`startDate`	No	Optional start date filter in YYYY-MM-DD format
`itemNumber`	No	Optional exact SEC current-report item number, e.g. 2.02, 5.02, or 1.01.
`documentType`	No	Document type filter: a registered value such as 'TenK', 'TenQa', 'EightK', 'TwentyF', 'Def14A', 'Defa14A', 'SThree' or 'TenderOfferThirdParty', or its SEC form name ('10-K', '20-F/A', 'DEFA14A', 'S-3ASR', 'SC TO-T', 'NT 10-Q'), plus deployment-registered types such as EarningsCallTranscript. An unrecognized value returns an error listing every accepted value.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / ticker / description

Previous value: -"Optional company ticker symbol (e.g., AAPL, MSFT). Omit for all companies."New value: +"Optional company ticker symbol (e.g., AAPL, MSFT); a listing outside the US is MIC:TICKER (e.g. XPAR:AIR), whose list includes its ESEF reports. Omit for all companies."

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / documentType / description

Previous value: -"Document type filter. Accepts a registered type value — 'TenK', 'TenQ', 'EightK', 'TenKa', 'TenQa', 'EightKa', 'TwentyF', 'SixK', 'FortyF', 'TwentyFa', 'SixKa', or 'FortyFa' — or its display name (e.g. '10-K', '20-F/A'), plus any deployment-registered type, such as EarningsCallTranscript (display name: Earnings Call) for earnings-call transcripts where available. An unrecognized value returns an error listing every accepted value."New value: +"Document type filter: a registered value such as 'TenK', 'TenQa', 'EightK', 'TwentyF', 'Def14A', 'Defa14A', 'SThree' or 'TenderOfferThirdParty', or its SEC form name ('10-K', '20-F/A', 'DEFA14A', 'S-3ASR', 'SC TO-T', 'NT 10-Q'), plus deployment-registered types such as EarningsCallTranscript. An unrecognized value returns an error listing every accepted value."

AddedAug 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), yet the description still adds real substance: hidden document types are excluded by default, EDGAR acceptance times are blank for filings stored before October 2026, and summary/viewer-URL fields appear only when the deployment supports them. These are non-obvious conditional behaviors an agent could not infer from the schema.

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 purpose and ordering, then scope selection, return fields, filters, and handoff. Dense and mostly waste-free, though 'Supports date, document-type, and exact SEC item-number filters' partly restates the schema and could be trimmed.

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 fully enumerates the returned columns (company identity, document IDs, types, dates, item numbers, line counts, accession numbers, acceptance times, page totals) including the UTC/blank caveat. It also covers conditional fields and the downstream ID handoff, so an agent needs nothing else to call and consume this tool.

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 100%, so the baseline is 3; the description earns more by adding semantics beyond the schema — the ticker argument's omit-vs-provide semantics, and the interaction between documentType and the hidden-type exclusion rule. It only lightly echoes the date and item-number filters that the schema already documents.

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 dual resource ('List stored SEC filings and earnings-call transcripts newest first'), plus ordering. It is clearly distinct from the Search* siblings, and the closing line 'Pass a returned ID to SearchDocument or ReadDocumentLines' positions it as the discovery step feeding those tools.

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?

Explicitly tells the agent how to choose scope: 'Omit ticker for a market-wide feed or provide one ticker for a company-specific list', and notes hidden types are excluded unless explicitly requested. It stops short of naming SearchDocuments/SearchDocument as the alternative for content-based lookup, so the search-vs-list choice is only implied.

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

All Equibles tools Inspect

Try in Browser