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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "get_edgar_filings"
  }
}

Input 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

NameRequiredDescriptionDefault
countNo
notesNo
companyYes
filingsYes
data_as_ofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / company / additionalProperties
      Previous value: -trueNew value: +{}
    • removedOutput schema / properties / company / properties / cik / anyOf
      Removed value: -[
      -  {
      -    "type": [
      -      "string",
      -      "number"
      -    ]
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / company / properties / cik / type
      Added value: +[
      +  "string",
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / market / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / market / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / page_url / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / page_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / source / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / source / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / stock_code / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / stock_code / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / company / properties / ticker / $ref
      Removed value: -"#/properties/company/properties/name_en"
    • addedOutput schema / properties / company / properties / ticker / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / data_as_of / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / filings / items / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed1 schema field changed
    • addedOutput schema / properties / data_as_of
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint, so the description adds non-redundant behavior: it returns metadata and URLs only and "does NOT download filing contents," coverage is the latest ~1000 filings per company, and an empty result usually signals an over-narrow filter. Error routing to search_edgar_company on unknown companies is a further operational detail beyond the annotations.

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 the key non-download caveat, then Args/Returns/Examples/Use-when blocks. Minor waste: the "Not this tool for" line and "Don't use for" line duplicate the same exclusion, and the Returns block largely mirrors the output schema.

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?

For a 5-parameter read tool it covers inputs, output shape and coverage limits, form-type semantics, worked examples, and failure modes. An agent has everything needed to call it correctly on the first attempt.

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 coverage is 100%, so the baseline is 3; the description mostly restates the schema (company accepts ticker/name/CIK, limit 1-50 default 20, YYYY-MM-DD range). It does add meaning for forms ("exact match, case-insensitive") and explains that 8-K rows carry 'items', which edges it above a pure restatement but not to a full 4.

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+resource ("List a US company's recent SEC filings ... from the EDGAR submissions index") and enumerates the covered form types. It immediately distinguishes itself from get_dart_filings and get_disclosure_feed, so an agent can route without opening the schema.

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?

Explicit when/when-not blocks: "Use when: you need filing dates, document links, or 8-K event items" and "Don't use for: Korean disclosures (get_dart_filings) or filing full-text search across all companies." It also names alternatives by tool name and supplies two worked examples, leaving nothing to inference.

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.