Skip to main content
Glama
daniel3303

Equibles

by daniel3303
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

List Filings

ListFilings
Read-only

List stored SEC filings and earnings-call transcripts newest first, optionally by ticker, date, document type, or SEC item number. Use returned IDs to search or read document lines.

Instructions

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. Pass a returned ID to SearchDocument or ReadDocumentLines.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (default: 1)
tickerNoOptional 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.
endDateNoOptional end date filter in YYYY-MM-DD format
maxItemsNoMaximum number of documents per page (default: 10)
startDateNoOptional start date filter in YYYY-MM-DD format
itemNumberNoOptional exact SEC current-report item number, e.g. 2.02, 5.02, or 1.01.
documentTypeNoDocument 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.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond readOnlyHint=true: return fields, UTC/blank acceptance times before October 2026, hidden document types excluded unless requested, and optional per-row summaries. These details materially inform expected results.

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 core list operation, then covers filtering, exclusions, optional summaries, and next-step routing. The length is justified by the tool's breadth, with no obvious 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?

No output schema exists, but the description explains returned identity, IDs, types, dates, item numbers, line counts, accession data, and page totals. Combined with annotations, it is complete enough to invoke correctly.

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 parameter documentation is already complete. The description still adds semantics by explaining ticker omission for market-wide feeds, date/document-type/item filters, and hidden-type behavior.

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 resource: lists stored SEC filings and earnings-call transcripts newest first. It clearly distinguishes market-wide versus ticker-specific listing, so the agent can identify the tool without opening schemas.

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?

Explains ticker usage and names SearchDocument and ReadDocumentLines as follow-up tools for IDs. It does not directly compare itself to SearchDocuments or exclude specific situations, but the usage context is clear.

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

Deploy Server

Other Tools