Skip to main content
Glama
stagproject

SEC EDGAR Filings MCP

by stagproject
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

search_filings

Search over 10,000 SEC filings by ticker, form type, or company. Returns a filtered catalog with readiness scores and URLs to shortlist filings for detailed analysis.

Instructions

PRIMARY discovery tool — lightweight catalog over 10k+ SEC filings (fi_listings_portfolio). [COST: low xpay per-call fee] Does NOT return alpha_signals, causality_events, or financial_metrics (use get_filing_sample / purchase_filing). Always returns agent_readiness_score (higher = better structured data) and edgar_url.

Required: at least one of ticker, form_type, company_name, fiscal_period, cik (avoids full-table scans).

Agent workflow after this call:

  1. Shortlist by agent_readiness_score and optional agent_one_liner

  2. get_filing_sample(document_id) — free preview

  3. purchase_filing(document_id) — paid full JSON (x402)

[EXAMPLE ARGUMENTS - MINIMAL]: {"ticker": "AAPL", "limit": 5}

"ticker": "ADM", "form_type": "10-Q", "company_name": "Archer", "fiscal_period": "2026Q1", "min_agent_readiness_score": 70, "limit": 20, "offset": 0, "include_one_liner": true }

[EXAMPLE ARGUMENTS - PAGINATION (page 2)]: {"ticker": "MSFT", "form_type": "10-K", "limit": 10, "offset": 10}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerNoTicker prefix, case-insensitive (e.g. AAPL, MSFT). At least one filter required.
form_typeNoSEC form: 10-K, 10-Q, 8-K, etc.
company_nameNoSubstring match on company_name (e.g. Apple, Archer-Daniels).
fiscal_periodNoFiscal period label (e.g. 2026Q1, 2025FY).
cikNoSEC CIK prefix (digits, e.g. 0000320193).
min_agent_readiness_scoreNoMinimum agent_readiness_score (0–100). Use 70+ for production-quality rows.
limitNoPage size (1–100). Default 10 keeps payloads small for LLM context.
offsetNoSkip rows for pagination (e.g. 10 for page 2 when limit=10).
include_one_linerNoIf true, adds agent_one_liner (~1 sentence) per row for triage without calling get_filing_sample. Slightly heavier response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses cost ('low xpay per-call fee'), limitations (no certain data), pagination behavior, and required filters. It could be more explicit about rate limits or idempotency, but overall it is transparent.

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?

The description is well-structured but somewhat verbose due to three examples. However, the structure (summary, cost, limitations, requirements, workflow, examples) is clear and each sentence adds value. The length is justified by the tool's complexity.

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?

Given the complexity (9 parameters, no required, output schema exists), the description covers purpose, exclusions, cost, required filters, pagination, and integration with siblings. It mentions key output fields and the workflow, making it comprehensive.

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 coverage is 100%, so baseline is 3. The description adds significant value beyond schema by explaining constraints (e.g., 'Default 10 keeps payloads small for LLM context'), providing examples, and clarifying the effect of parameters like include_one_liner and min_agent_readiness_score.

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 clearly states it is a 'PRIMARY discovery tool' for searching SEC filings, using specific verbs and resource references. It distinguishes from siblings by explicitly stating what it does NOT return and directing to get_filing_sample/purchase_filing for other data.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance: lightweight catalog vs. advanced tools. It specifies required filter conditions ('at least one of ticker, form_type...') and outlines the post-call workflow (shortlist, sample, purchase).

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

Deploy Server

Other Tools