Skip to main content
Glama

Company filings and key financials from SEC EDGAR

sec_filings
Read-only

SEC EDGAR profile and latest filings for a ticker or CIK: company name, CIK, SIC code and industry, fiscal year end, state of incorporation, tickers and exchanges, plus the newest filings of selected forms (10-K, 10-Q, 8-K, 20-F, 6-K, S-1, DEF 14A, 4, 13F-HR, SC 13G) with filing and report dates, accession number, 8-K items and primary document URL. Optional latest XBRL revenue, net income, total assets and cash. Sources: SEC EDGAR submissions and XBRL APIs. Price: $0.01 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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": "sec_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key, 1 to 10 digits. Mutually exclusive with ticker.
formsNoComma-separated form types from: 4, 10-K, 10-Q, 8-K, 20-F, 6-K, S-1, DEF 14A, 13F-HR, SC 13G (default 10-K,10-Q,8-K). SC 13G also matches SCHEDULE 13G.
limitNoFilings to return, 1 to 20 (default 10), newest first.
tickerNoStock ticker, e.g. AAPL or BRK.B. Mutually exclusive with cik.
amendmentsNoAlso match /A amendments of the selected forms (default false).
financialsNoAdd the latest 10-K/10-Q XBRL values for revenue, net income, total assets and cash (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description goes beyond them with genuinely useful operational facts: the upstream sources (EDGAR submissions and XBRL APIs), the $0.01 per-successful-call x402 v2 USDC charge, and the guarantee that failed or no-match calls are free. That billing detail materially affects how an agent should retry and batch calls.

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?

Front-loaded with the purpose in the first clause, then the return fields, then sources and pricing. The long field enumeration is dense but every item tells the agent what it can rely on getting back. A separate final sentence for pricing keeps cost information from being buried.

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?

With no output schema, the description correctly takes on the job of describing return values, and it does so field by field. Cost and charging behavior are covered. What's missing is any note on response shape, error behavior beyond billing, or rate limits, which are minor gaps for a read-only lookup.

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 every parameter already carries its own description, enum and examples. The description only restates defaults (fixed form set, latest XBRL values) and never adds syntax or constraint detail beyond the schema. Baseline 3 is the right ceiling when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (SEC EDGAR company profile plus latest filings) and enumerates exactly what comes back: CIK, SIC code, fiscal year end, state of incorporation, form types, accession numbers and document URLs. That is far more concrete than a restated title. It doesn't contrast itself with the sibling company_profile, so an agent must infer when EDGAR data is the right source.

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

Usage Guidelines3/5

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

Usage is only implied: the mention of a ticker or CIK and the form list lets an agent infer this is for public-company regulatory filings. There is no explicit when-to-use, when-not-to-use, or pointer to company_profile as the alternative for non-SEC company data. Adequate but leaves routing to inference.

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