Skip to main content
Glama

SEC EDGAR full-text search of company filings

sec_search
Read-only

Full-text search of SEC EDGAR filings since 2001 (10-K, 10-Q, 8-K, proxy, S-1, exhibits and more): keywords, "exact phrase", OR, NOT, NEAR and trailing * wildcard, filtered by form type, ticker or CIK and filing date range. Returns total hits, hits by form, top filers and matching documents with company, CIK, ticker, form, filing date, period, accession number, 8-K items and sec.gov document URL. Insider Forms 3, 4, 5 and 144 excluded. Source: SEC EDGAR Full-Text Search. Price: $0.005 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing 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
qYesKeywords or "exact phrase", 2 to 200 characters. All terms are required; OR between terms, NOT or a leading - to exclude, word NEAR(n) word for proximity (default 10 words) and a trailing * wildcard on a 3+ character stem (not inside a phrase, excluded, or next to OR).
cikNoOnly documents filed by or about this SEC Central Index Key, 1 to 10 digits; individual (natural-person) filers are not served. Mutually exclusive with ticker.
sortNoResult order: relevance (default), newest or oldest filing date.
formsNoComma-separated EDGAR form types, e.g. 10-K,10-Q,8-K,DEF 14A,S-1. A form also matches its /A amendments; list only /A forms to match amendments alone. Default: all forms except 3, 4, 5, 144 and MA-I (never searched).
limitNoDocuments to return, 1 to 50 (default 10).
tickerNoOnly documents filed by or about this company, by stock ticker (e.g. AAPL). Mutually exclusive with cik.
end_dateNoLatest filing date, YYYY-MM-DD. Default: today.
start_dateNoEarliest filing date, YYYY-MM-DD. Default: no lower bound (coverage starts 2001).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Read-only and open-world behavior are already declared in annotations, so the added value is the billing model: $0.005 per successful call in USDC via x402, with failed and zero-match calls free. Notably, the description states the tool 'Returns total hits, hits by form, top filers and matching documents' even though the context indicates no output schema, which is helpful return-shape context.

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?

Information is front-loaded: query syntax first, then filters, returns, exclusions and price. It is dense but each clause carries useful content; the pricing sentence at the end is slightly tacked-on but still earns its place.

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 search tool with no output schema, the description covers query syntax, filter dimensions, return fields, exclusions and cost. Nothing material needed to invoke it correctly is missing.

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?

With schema coverage at 100%, the schema already documents q operators, forms, cik/ticker exclusivity, sort, limit and dates. The description mostly restates those filters; the only additional meaning is the insider-form exclusion, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource plus scope: 'Full-text search of SEC EDGAR filings since 2001' with enumerated form types. It is clear what the tool does, but it never names or contrasts a sibling such as sec_filings, so differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Coverage boundaries (since 2001, Forms 3/4/5/144 excluded, MA-I never searched) imply when this search is appropriate. However there is no explicit 'use this instead of X when...' guidance against the sibling listing tools.

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