Skip to main content
Glama

List recent SEC EDGAR filings for a company

sec_filings
Read-only

Recent SEC EDGAR filings of a company (10-K, 10-Q, 8-K and more), found by ticker, CIK or name. A name that matches several filers returns candidates with HTTP 400, not charged. Each filing gives the form, filing and report dates, description, index page and primary document. Source: SEC EDGAR, public domain. Related tools on this server, for a different need: sec_events when you need to list a US company's latest 8-K filings and their items; sec_search when you need to search SEC EDGAR filings by full text. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "company": "<company>"
    },
    "name": "sec_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
formsNoComma-separated form types, e.g. 10-K,10-Q,8-K. Default: all
limitNoMax filings, 1-50, default 10
companyYesTicker (AAPL), CIK (320193) or company name

Output Schema

NameRequiredDescriptionDefault
noteNo
formsNo
sourceNo
companyNo
filingsNo
returnedNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checkedAt": {},
      +    "company": {},
      +    "filings": {},
      +    "forms": {},
      +    "note": {},
      +    "returned": {},
      +    "source": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses error behavior (HTTP 400 with candidate filers on ambiguous names), billing behavior ($0.002 per successful call, failed calls not charged), and the payment mechanism (x402, USDC on Base, Solana and others). The only gap is pagination, which is minor given the limit parameter and output schema.

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 purpose and scope are front-loaded, followed by the sibling routing and then the commercial terms, which is a sensible order. The pricing sentence carries some avoidable bulk (enumerating Solana and "10 more networks") for information that rarely affects tool selection.

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?

For a three-parameter, read-only lookup with an output schema and annotations already supplied, the description covers what an agent still needs: routing to alternatives, ambiguous-name failure handling, and cost. Nothing required to invoke it correctly is missing.

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 description coverage is 100%, so the schema already documents forms, limit and company with examples. The description restates the accepted lookup keys (ticker/CIK/name) and form examples but adds no format or constraint detail beyond the schema, so the baseline of 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?

The description states a specific verb and resource ("Recent SEC EDGAR filings of a company"), names the form types covered, and specifies the lookup keys (ticker, CIK or name). It also explicitly distinguishes itself from sec_events and sec_search, so an agent can choose without opening either schema.

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?

It gives explicit routing rules: use sec_events for a US company's latest 8-K filings and their items, and sec_search for full-text search. It also states the failure condition (an ambiguous name returns HTTP 400 with candidate filers), which is exactly the guidance an agent needs before supplying a free-text company name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources