Skip to main content
Glama

SEC company profile and filings

sec_company
Read-only

Look up a US public company in SEC EDGAR by ticker or CIK: legal name, exchange, industry, state, fiscal year end, and its latest filings (10-K, 10-Q, 8-K, insider Form 4 and more) with direct links. Filter by form type, e.g. only 10-Ks.

$0.002 USDC per call over x402. Failed calls cost nothing. Call without payment to get a quote.

When to use: You need who a US public company is, or links to its recent filings. Use instead: sec_financials for the numbers; company_snapshot for profile plus numbers; company_due_diligence for ratios and 8-K summaries. Parameters: ticker or cik (one is required). form: only this form type, e.g. 10-K, 10-Q, 8-K or 4. limit: 1-40 filings, default 10. Returns: name, CIK, exchange, industry, state, fiscal year end, and filings[] with form, date and link.

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

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key, e.g. 320193. Give this or ticker.
formNoOnly this form type, e.g. "10-K".
limitNoHow many filings, 1-40 (default 10).
tickerNoUS stock ticker, e.g. "AAPL". Give this or cik.
paymentNoBase64 x402 payment payload. Omit it to receive a quote; sign that and call again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cik / description
      Added value: +"SEC Central Index Key, e.g. 320193. Give this or ticker."
    • addedInput schema / properties / limit / description
      Added value: +"How many filings, 1-40 (default 10)."
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations cover read-only and open-world safety, but the description adds the non-obvious commercial behavior: $0.002 USDC per call over x402, failed calls are free, and omitting `payment` returns a quote that must be signed and re-called. It also discloses the return shape. It stops short of describing error behavior when a ticker or CIK resolves to nothing, which would be the last missing piece.

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?

Front-loaded purpose, then pricing, then when-to-use, then alternatives, then parameters and returns — a clean scan order. Minor redundancy where the parameter and returns lines paraphrase what the schema already declares.

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?

With no output schema and five parameters, the description still covers cost/payment flow, required-input semantics, filtering, limits, and the exact returned fields. An agent has everything needed to call it and to interpret the response.

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, but the description adds a genuinely new constraint the schema does not express: one of ticker or cik is required (the schema marks zero required properties). It also gives concrete form-type examples and restates the 1-40 limit range and default.

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?

States a specific verb and resource ("Look up a US public company in SEC EDGAR by ticker or CIK") plus the exact payload (profile fields and filings with links). The section headers make it trivially distinguishable from sec_financials, company_snapshot, and company_due_diligence.

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?

Explicit "When to use" and "Use instead" lines name three sibling tools and the condition that selects each, plus a concrete parameter tip (filter by form type, e.g. only 10-Ks). No routing is left 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.