Skip to main content
Glama
SEC EDGAR, UK Companies House & LEI MCP Server

SEC EDGAR, UK Companies House & LEI MCP Server

by willowswt

search_sec_edgar_filings_fulltext

Read-onlyIdempotent

Search full text of SEC EDGAR filings by keyword or phrase and filter by form type or start date to locate disclosures such as cybersecurity incidents or going concern.

Instructions

Full-text search across official US SEC EDGAR filings via EFTS (efts.sec.gov) for any keyword or phrase (e.g. 'cybersecurity incident', 'material weakness', 'artificial intelligence', 'going concern'), with optional form filter (forms like '10-K,8-K') and start date (startDate YYYY-MM-DD).

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": {
      "query": "<query>"
    },
    "name": "search_sec_edgar_filings_fulltext"
  }
}

Input Schema

NameRequiredDescriptionDefault
formsNoOptional comma-separated forms (e.g. '10-K,10-Q,8-K', default '10-K,10-Q,8-K').10-K,10-Q,8-K
queryYesExact phrase or keyword query to search across SEC filings.
startDateNoOptional start date YYYY-MM-DD (e.g. '2025-01-01').
maxResultsNoMax hits to return (1-25, default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the description is not carrying the safety burden. It adds useful context — the underlying EFTS endpoint and that matching is full-text over filing text — but says nothing about SEC EDGAR's aggressive rate limits, result ordering/relevance, or pagination depth, which materially affect correct invocation.

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?

A single front-loaded sentence that puts the resource and mechanism first. It is somewhat dense — four illustrative query examples and two parenthetical parameter recaps — but no sentence is pure filler.

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

Completeness3/5

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

The tool is read-only and simple, and all four parameters are schema-documented, but with no output schema the description never indicates what a hit contains (company name, form type, filing date, matched snippet, URL). For an agent deciding whether this tool answers its question, that return-shape gap matters.

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 description coverage is 100%, so the baseline is 3. The description nonetheless reinforces the two most error-prone parameters by restating concrete formats ('forms' like '10-K,8-K' and 'startDate' YYYY-MM-DD), which helps avoid malformed values, though it omits the fourth parameter (maxResults) entirely.

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 names a specific verb and resource ('Full-text search across official US SEC EDGAR filings via EFTS'), plus the scope ('any keyword or phrase'). That is clearly separable from the sibling tools, which look up CIK identifiers, XBRL facts, UK Companies House records, and LEI ownership — none of which is a keyword search over filing text.

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?

The parenthetical query examples ('cybersecurity incident', 'going concern') implicitly signal when this tool fits, but there is no explicit routing guidance such as 'use lookup_public_company_cik_and_filings when you know the company, use this when you only have a topic.' Nor are any exclusions or prerequisites stated.

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