Skip to main content
Glama

FinBridge

by kr.gronox.mcp

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.

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. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description reinforces this by stating it does NOT download filing contents and that the caller must fetch the returned URL. It also discloses meaningful behavior beyond the schema: exact-match case-insensitive form filtering, a ~1000-filing window, and 8-K items. These details add real value.

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 labeled sections (Args, Returns, Use when, Don't use, Errors) and front-loads the most important behavioral constraint—no content download—immediately. Examples and error guidance justify the length; no sentence is wasted.

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 read-only list tool with a rich output schema, the description covers the return shape, parameter constraints, usage boundaries, and error recovery. It is complete enough for an agent to call the tool correctly and interpret results without additional inference.

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, but the description adds useful semantics beyond the schema: the exact-match and case-insensitive nature of forms, the ~1000-filing window implication, and the practical interpretation of company as ticker/name/CIK with examples like 'BRK-B' or 'BRK.B'. This lifts it above baseline.

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 opens with a specific verb and resource: 'List a US company's recent SEC filings' from the EDGAR submissions index. It clearly distinguishes itself from sibling tools by stating it returns metadata and document URLs only, not contents, and by naming Korean disclosures and full-text search as exclusions.

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 'Use when' and 'Don't use for' sections name the exact conditions and alternatives, including get_dart_filings for Korean disclosures and full-text search for all companies. It also gives error guidance to use search_edgar_company for unknown companies, which fully routes the agent to the correct tool.

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

All FinBridge toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools have clearly distinct resource+action targets, and the overlapping screen_* tools are thoroughly cross-referenced with 'use screen_X instead' guidance. Minor ambiguity exists between get_disclosure_feed, get_dart_filings, and get_dart_major_events, which all surface KR filings from different angles but remain distinguishable.

Naming Consistency5/5

Every tool follows a consistent verb_noun snake_case pattern: get_* for retrievers, screen_* for screeners, search_* for lookups, plus action verbs like analyze_, backtest_, compare_, import_, and query_. Subfamilies (dart_*, edgar_*, fred_*, crypto_*) are consistently prefixed, making tool selection predictable.

Tool Count3/5

37 tools is heavy, and the four momentum screeners (canslim/kell/minervini/schwartz) plus three KR disclosure tools could arguably be collapsed into parameterized variants. However, the server's unusually broad scope—KR/US/TW/JP/EU equities, crypto, macro, portfolio, backtesting—means most tools earn their place, so the count is high but not chaotic.

Completeness4/5

The surface covers the core workflow well: search, prices, fundamentals, filings, insider trades, valuation, screeners, backtesting, and portfolio tracking for KR/US, plus crypto and macro. Notable gaps are the lack of single-company financial-statement tools for TW/JP/EU (only available through screen_companies) and no real-time stock quotes, but these are workable for the stated local-database research purpose.

Resources