Skip to main content
Glama
brechanbech

SEC EDGAR MCP

by brechanbech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

Full-Text Filing Search

sec_full_text_search
Read-only

Search SEC filing full text from 2001 onward, including exhibits, to find companies by what they said without knowing the company upfront. Filter by form, ticker, or date range.

Instructions

Search the full text of SEC filings from 2001 onward, exhibits included — the one tool here that finds companies by what they SAID rather than needing the company up front (e.g. which filers discussed a climate transition plan). Wrap a phrase in double quotes inside the query for an exact match. Leave the query out, with a form filter or a date range, to list filings by form and date instead, one per filing, newest first: e.g. every Schedule 13D filed last week. Optionally filter by form, ticker and date range; a form filter excludes amendments (e.g. '10-K/A') unless include_amendments is set, and any amendment returned is marked 'amendment': true. Each hit comes back with a direct URL to the matching document. To page, pass next_offset back as offset — filtering means a page can return fewer than limit hits. Note the total saturates at 10000, flagged by total_is_lower_bound, and counts excluded amendments, flagged by total_is_upper_bound (or total_is_approximate when both apply).

Input Schema

NameRequiredDescriptionDefault
formsNoOptional filter: '10-K', '8-K', or several comma-separated ('10-K,10-Q'). Amendments are excluded unless requested: '10-K' returns original 10-Ks only, '10-K/A' returns amendments only, '10-K,10-K/A' returns both.
limitNoNumber of hits to return (default 10, max 100)
queryNoWords or phrase to find in filing text. Wrap in double quotes for an exact phrase: "climate transition plan". Unquoted terms match separately. Omit it, with 'forms' or a date range, to list filings by form and date, one per filing, newest first.
offsetNoNumber of hits to skip, for paging past the first page (default 0)
tickerNoOptional: restrict to one company by ticker or CIK
end_dateNoOptional latest filing date, YYYY-MM-DD
start_dateNoOptional earliest filing date, YYYY-MM-DD
include_amendmentsNoAlso return amendments ('10-K/A') of the requested forms (default false). Amendments are often partial (only Part III, or one exhibit) or restatements that supersede the original's figures.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.0
    • changedInput schema / properties / query / description
      Previous value: -"Words or phrase to find in filing text. Wrap in double quotes for an\nexact phrase: \"climate transition plan\". Unquoted terms match separately."New value: +"Words or phrase to find in filing text. Wrap in double quotes for an\nexact phrase: \"climate transition plan\". Unquoted terms match separately.\nOmit it, with 'forms' or a date range, to list filings by form and date,\none per filing, newest first."
    • removedInput schema / required
      Removed value: -[
-  "query"
-]
  2. Changed1 schema field changedv0.7.0
    • changedInput schema / properties / ticker / description
      Previous value: -"Optional: restrict to one company by ticker"New value: +"Optional: restrict to one company by ticker or CIK"
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior beyond them — amendments are excluded from form filters unless include_amendments is set and returned amendments are flagged, each hit carries a direct document URL, paging can yield fewer than `limit` hits when filtering, and `total` saturates at 10000 with distinct lower/upper/approximate bound flags. These are exactly the non-obvious traits an agent needs before trusting results.

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 sibling differentiator, and every sentence carries operational information (quoting, listing mode, amendment semantics, paging, total flags). It is dense to the point of being slightly packed — several parenthetical caveats chain together — but no sentence is 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?

For an 8-parameter, no-required-parameter search tool with no output schema, the description covers both search modes, filtering interactions, result shape (URL per hit), paging, and the semantics of the total counters. Nothing material is left for the agent to discover by trial.

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 already 100%, but the description still adds meaning: it explains the offset/next_offset paging contract and the consequence of filtering on page size, and explains the forms/include_amendments interaction at a semantic level. It stops short of documenting ticker/CIK acceptance details beyond the schema, so it is strong rather than exhaustive.

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 ('Search the full text of SEC filings from 2001 onward, exhibits included') and explicitly positions itself against siblings as the tool that finds companies by content rather than by company identifier. The example query ('which filers discussed a climate transition plan') makes the distinction concrete.

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?

Gives explicit when-to-use guidance (when you don't have the company up front, unlike other tools here) plus a distinct alternative mode: omit the query with a form filter or date range to list filings by form and date, with a worked example (Schedule 13D last week). It also names the quoting convention for exact phrase matching.

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