Skip to main content
Glama

FinBridge

List SEC Filings

get_edgar_filings
Read-only

List a US company's recent SEC filings (10-K, 10-Q, 8-K, S-1, proxy statements, Form 4, ...) from the EDGAR submissions index. Returns metadata and document URLs only — it does NOT download filing contents; fetch the returned url yourself for the document text.

Not this tool for: Korean filings (get_dart_filings) or a cross-market feed already stored here (get_disclosure_feed).

Args:

  • company (required): ticker / company name / CIK

  • forms: optional form-type filter, e.g. ['10-K'] or ['10-K','10-Q','8-K'] (exact match, case-insensitive)

  • from / to: optional YYYY-MM-DD filing-date range

  • limit: max rows, 1-50 (default 20)

Returns: {company:{cik, name, ticker}, count, filings:[{form, filingDate, accessionNumber, primaryDocument, items?, url}], notes?}. 8-K rows include 'items' (e.g. '2.02,9.01' = results of operations + exhibits). Coverage = the latest ~1000 filings per company.

Examples:

  • "Apple's latest annual report" -> {company:'AAPL', forms:['10-K'], limit:1} then fetch the url

  • "Tesla 8-Ks this year" -> {company:'TSLA', forms:['8-K'], from:'2026-01-01'}

Use when: you need filing dates, document links, or 8-K event items for a US company. Don't use for: Korean disclosures (get_dart_filings) or filing full-text search across all companies.

Errors: unknown company -> use search_edgar_company; an empty result usually means the form/date filter is too narrow for the ~1000-filing window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLatest filing date, YYYY-MM-DD
fromNoEarliest filing date, YYYY-MM-DD
formsNoForm types to include, e.g. ['10-K','8-K']. Omit for all forms
limitNoMax filings to return (default 20)
companyYesUS company: ticker (e.g. 'AAPL', 'BRK-B' or 'BRK.B'), company name, or CIK number

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
notesNo
companyYes
filingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

The description is transparent about read-only behavior, coverage limits (~1000 filings per company), error handling, and the fact that it only returns metadata/URLs and does not fetch full documents. This aligns perfectly with the readOnlyHint and destructiveHint annotations.

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 well structured with clear sections for purpose, examples, usage boundaries, and errors. It is detailed but every sentence adds value, and the included examples improve clarity without redundancy.

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?

The description, schema, and output schema together provide complete context: parameters, return shape, coverage limits, error handling, and disambiguation from sibling tools. No critical information is missing for an agent to invoke this tool correctly.

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?

The schema covers 100% of parameters with meaningful descriptions, and the tool description further clarifies company formats, form-type filtering, date range syntax, and limit defaults. Examples make parameter usage concrete.

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 description clearly states that the tool lists a US company's recent SEC filings from EDGAR, returns metadata and document URLs, and does not download contents. It also distinguishes itself from sibling tools like get_dart_filings and get_disclosure_feed.

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 provides explicit use cases, examples, and a 'Use when' / 'Don't use for' section that clearly scopes the tool. It also explains likely errors and empty results, giving strong practical guidance.

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.