SEC EDGAR Company Lookup

sec_company_filings

Pull a US-listed company's official SEC profile, latest filings and headline financials. By ticker, CIK or name: CIK, SIC, state, addresses, former names, latest filings with a form filter and direct document links, plus XBRL figures (revenue, net income, assets, liabilities, equity, cash, shares) with period and filing reference, straight from SEC EDGAR. Use when you need primary-source data on an SEC registrant. $0.002 per call, USDC on Base (x402).

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_company_filings"
  }
}

Input Schema

Name	Required	Description
`cik`	No	CIK
`name`	No	Company name
`forms`	No	Form filter, e.g. 10-K,8-K
`limit`	No	Max filings (default 10)
`ticker`	No	Ticker
`financials`	No	Include financials (default true)
`payment_signature`	No	x402 v2 PAYMENT-SIGNATURE header value. Omit to receive payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the two most consequential behaviors: the data is pulled directly from SEC EDGAR (primary source, implying a read-only operation) and the call costs $0.002 via USDC on Base through x402. It does not cover rate limits, error behavior, or what happens when no identifier is supplied, which are relevant for a paid network call.

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?

Three sentences, front-loaded with purpose and followed by scope, then the usage trigger and cost. Dense but every clause carries information. The middle sentence is a long comma-and-parenthesis list that is slightly harder to scan than the rest.

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?

There is no output schema, and the description compensates by enumerating the returned fields (CIK, SIC, state, addresses, former names, filings with document links, XBRL figures). Combined with the payment model and identifier options, an agent has everything needed to call this correctly on the first attempt.

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 the baseline is 3, but the description adds real meaning: it states the three accepted identifier modes ("By ticker, CIK or name") and enumerates which XBRL figures come back (revenue, net income, assets, liabilities, equity, cash, shares), tying the financials flag and forms filter to concrete output. It stops short of explaining what occurs if multiple identifiers are passed or none at all.

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 opens with a specific verb and resource — "Pull a US-listed company's official SEC profile, latest filings and headline financials" — and names the authoritative source (SEC EDGAR). An agent immediately knows both the action and the data domain, with no sibling tools to disambiguate against.

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?

It gives an explicit usage trigger: "Use when you need primary-source data on an SEC registrant." That cleanly separates it from secondary/derived financial data sources. There are no alternatives or exclusions to state since no siblings exist, but it also doesn't say when this tool is the wrong choice (e.g., non-US registrants).

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

All SEC EDGAR Company Lookup tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?