Skip to main content
Glama
SEC EDGAR MCP

SEC EDGAR MCP

by reblickulous

search_filings

Find recent SEC filings for a company by CIK number, optionally filtered by form type, and return dates, accession numbers, and document names for retrieval.

Instructions

Get recent SEC filings for a company using its CIK number. Optionally filter by form type (10-K, S-1, 8-K, DEF 14A, etc.). Returns filing dates, accession numbers, and document names needed for fetch_filing.

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": {
      "cik": "<cik>"
    },
    "name": "search_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesCompany CIK number from lookup_company (e.g. '1318605')
limitNoMax number of results to return (default 15)
form_typeNoFilter by form type: 10-K, 10-Q, S-1, 8-K, DEF 14A, Form D, etc. Leave blank for all recent filings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden and does part of the job: it names the returned fields (filing dates, accession numbers, document names), which substitutes for a missing output schema. It does not state ordering guarantees beyond 'recent', what happens for an invalid or unknown CIK, SEC EDGAR rate limits, or result truncation behavior.

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?

Three short sentences, front-loaded with the action and key input, followed by the optional filter and then the return/next-step payoff. No filler and every clause carries information an agent needs.

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?

For a simple three-parameter read tool with full schema coverage, the description covers purpose, optional filtering, returned fields, and the handoff to fetch_filing. The only shortfall is the absence of annotations paired with no mention of failure modes or pagination, which matters slightly more when nothing structured carries that information.

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%, so all three parameters are already documented in the schema, including the CIK derivation from lookup_company and the form-type examples. The description only restates the optional form-type filter, adding no format or validation detail beyond the schema, so baseline 3 applies.

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 ('Get recent SEC filings for a company'), names the keying mechanism (CIK), and distinguishes itself from the fetch step by saying the results feed fetch_filing. An agent can tell immediately what this tool returns and how it differs from lookup_company and fetch_filing.

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?

Implies the search-then-fetch workflow by noting the output is 'needed for fetch_filing', and explains the optional form-type narrowing. It gives clear context for when to use the tool but offers no explicit exclusions or guidance on when another sibling would be preferable.

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