Skip to main content
Glama

Filings index

filings_list
Read-onlyIdempotent

List a company's filings newest first: accession number, form type (10-K, 10-Q, 8-K, 20-F, 40-F, 6-K and others), filing date, acceptance time, period end, fiscal year and period, the primary document and its SEC URL, and the filing it amends. Filter by form; as_of limits the list to filings known on a date; cursor pages through long histories. Use filing_get for one filing's details and financials_as_reported to read its numbers.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "form": "10-K",
      "limit": 5,
      "company": "ticker:AAPL"
    },
    "name": "filings_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
formNoOptional form type filter, for example "10-K", "10-Q", "8-K", "20-F".
as_ofNoKnowledge date or timestamp (YYYY-MM-DD or RFC 3339). The answer is what FinancialMD knew at that instant: only facts whose known interval contains as_of. Omit for the current view.
limitNoMaximum number of periods or items to return (default 50, at most 500).
cursorNoOpaque cursor from a previous page (data.next_cursor).
companyYesCompany identifier: a FinancialMD id ("fmd_01H..."), an SEC CIK ("cik:320193"), or a ticker ("ticker:AAPL", optionally with the MIC "ticker:AAPL.XNAS"). A bare ticker like "AAPL" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI ("lei:IOG4E947OATN0KJYSD45") or its fmd_ id.

Output Schema

NameRequiredDescriptionDefault
dataNo{ items: [{ accession, registry, form, period_end, fiscal_year, fiscal_period, filed, accepted_at, primary_doc, source_url, amends, pipeline_version }], next_cursor }.
metaNoRequest metadata: request_id, as_of, company resolution, coverage, pipeline_version, licence, terms, proof_base.
errorNoPresent only on isError results: the API error code and message plus remedy hints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / company / description
      Previous value: -"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL."New value: +"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI (\"lei:IOG4E947OATN0KJYSD45\") or its fmd_ id."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavior: newest-first ordering, point-in-time semantics for as_of, and cursor-based paging of long histories. It does not discuss result caps beyond the schema's limit default, but the output schema covers the return shape.

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-loads the verb and resource, then packs filtering, point-in-time, and paging into a single tight clause before a routing sentence. The long field enumeration is somewhat redundant given an output schema exists, but it remains readable and earns most of its space.

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 full annotation coverage, 100% schema description coverage, and an output schema, the definition supplies everything an agent needs: scope, ordering, filtering, point-in-time behavior, pagination, and sibling routing. No material gap remains for a list tool of this complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description reinforces the role of form, as_of and cursor in one clause but adds no syntax, format, or edge-case detail beyond what the schema already documents for those parameters.

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 ("List a company's filings newest first") and enumerates the returned fields, so an agent knows exactly what comes back. It also distinguishes itself from filing_get and financials_as_reported by name, making it separable from siblings without opening a 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 clear operational context: filter with form, constrain with as_of, paginate with cursor, and route to filing_get for a single filing or financials_as_reported for numbers. It stops short of naming search-oriented siblings such as filing_search, so it is not a fully exhaustive when-to-use/when-not-to-use statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources