Skip to main content
Glama

Search SEC EDGAR filings by full text

sec_search
Read-only

Full-text search of SEC EDGAR filings: company, CIK, form, filing date, file name, a link to the matched document, its file type (e.g. EX-99.1) and the 8-K items. Results are in EDGAR relevance order; a total of 10,000 means at least that many. Filter by form types (e.g. 8-K,10-K) and filing dates. Results are capped at 20. US government data. Related tools on this server, for a different need: sec_filings when you need to list recent SEC EDGAR filings for a company; sec_events when you need to list a US company's latest 8-K filings and their items. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "sec_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWords, or a "phrase" in quotes
toNoTo date, YYYY-MM-DD
fromNoFrom date, YYYY-MM-DD
formsNoForm types separated by commas, e.g. 8-K,10-K
limitNo1 to 20 (default 10)

Output Schema

NameRequiredDescriptionDefault
hitsNo
orderNo
queryNo
totalNo
sourceNo
checkedAtNo
attributionNo
totalIsLowerBoundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / order
      Added value: +{}
    • addedOutput schema / properties / totalIsLowerBound
      Added value: +{}
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the sort order (EDGAR relevance), how to interpret the total count ('10,000 means at least that many'), that results are capped at 20, and the metered pricing model including that failed calls are not charged. The pay-per-call requirement via x402 is exactly the kind of behavioral detail an agent must know before invoking.

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?

Purpose and returned fields are front-loaded, then filters, then siblings, then price, which is a sensible order. The price sentence is the weakest link, padding with 'Solana and 10 more networks', but the cost figure itself is essential and not wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers what a caller needs for a metered, capped search endpoint: what it queries, how results are ordered and bounded, how to interpret the total, and what it costs. Because an output schema exists, the field enumeration is partly redundant, and a note on empty-result behavior would round it out.

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% and each parameter already carries a description, so the schema does most of the work. The description reinforces form filtering ('e.g. 8-K,10-K'), date filtering, and the 20-result cap that bounds the limit parameter, but adds no syntax or precedence details beyond the schema. Baseline 3 is appropriate.

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 ('Full-text search of SEC EDGAR filings') and enumerates the returned fields (company, CIK, form, filing date, file name, matched document link, file type, 8-K items). It also names the two closest siblings and the distinct need each serves, so an agent can separate it from sec_filings and sec_events without opening any 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 explicit routing context: 'sec_filings when you need to list recent SEC EDGAR filings for a company; sec_events when you need to list a US company's latest 8-K filings and their items', which covers the main alternatives. It stops short of stating an explicit when-not-to-use condition or prerequisites (e.g. what to do if full-text yields nothing).

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