SEC EDGAR MCP

get_recent_filings

Retrieve recent SEC EDGAR filings for a specific company or all filers. Filter by ticker/CIK, form type, and time window to access filing dates, accession numbers, and direct SEC URLs.

Instructions

Get recent SEC filings for a company or across all filers.

Args: identifier: Company ticker/CIK (optional, omit for all recent filings) form_type: Filter by form type (e.g., "10-K", "10-Q", "8-K", "4") days: Number of days to look back (default: 30) limit: Maximum filings to return (default: 50)

Returns: List of filings with dates, form types, accession numbers, and SEC URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_recent_filings"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No
`limit`	No
`form_type`	No
`identifier`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.8May 30, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It states it returns a list with specific fields, but does not disclose any behavioral traits like read-only nature, rate limits, or authorization needs. Adequate but could be more transparent.

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?

Description is a well-structured docstring with a summary line, Args section, and Returns section. It is concise with no fluff, front-loading the main purpose.

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?

The description explains return values (list with dates, form types, accession numbers, SEC URLs). With 4 parameters and no output schema, it is fairly complete, though missing details on ordering, pagination, or error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so description fully compensates. It explains each parameter (identifier, form_type, days, limit) with meaning and defaults, adding significant value beyond the schema which only provides names and types.

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?

Description clearly states the tool gets recent SEC filings for a company or across all filers. The verb 'get' and resource 'recent SEC filings' are specific, and it distinguishes from sibling tools like get_filing_content and get_filing_sections.

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?

Description provides parameters like identifier (optional), form_type, days, limit, implying when to use. However, it does not explicitly mention alternatives or when not to use, lacking explicit guidance.

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