Skip to main content
Glama
stagproject

SEC EDGAR Filings MCP

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
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses cost, that it does not return alpha_signals/events/metrics, and that it always returns agent_readiness_score and edgar_url. Also notes required filters for performance.

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?

Well-structured with front-loaded purpose, then key constraints, workflow, and examples. Each sentence adds value, though slightly verbose. Could trim redundant phrasing, but overall efficient.

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?

Given the tool has 9 parameters, no annotations, and an output schema (not shown), the description adequately covers return fields and usage context. Workflow integration with sibling tools is clearly explained.

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 baseline is 3. The description adds value through examples, cost hints, and usage context (e.g., 'limit default 10 keeps payloads small'), enhancing understanding beyond the schema.

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 the 'PRIMARY discovery tool' for SEC filings, a lightweight catalog. It distinguishes from siblings (get_filing_sample, purchase_filing) with specific details about what it does and does not return.

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?

Provides explicit when-to-use: as the first step in a workflow, with required filters to avoid full-table scans. Includes workflow steps after the call and examples of minimal and maximal arguments, guiding usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stagproject/sec-filings-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server