Skip to main content
Glama
brechanbech

SEC EDGAR MCP

by brechanbech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

Look Up CIK

sec_lookup_cik
Read-only

Look up an SEC CIK by exact ticker or by name to retrieve EDGAR company pages and filings. Use it when you have only a company, fund, or person name and need the matching CIK.

Instructions

Look up the SEC CIK (Central Index Key) by ticker or by name. With 'ticker', the ticker is matched exactly, ignoring case, against SEC's list of active tickers, which is fetched once and cached for an hour, so repeat lookups make no further SEC request. Returns one CIK, zero-padded to 10 digits, with a link to the company's EDGAR page; share classes such as GOOG and GOOGL map to the same CIK. An unknown ticker is an error, not a guess. Given a CIK as 'ticker', this returns the company's name and current tickers, which confirms whose it is. With 'name', this searches every EDGAR filer, including those with no ticker: fund managers such as Bridgewater, private issuers, delisted or acquired companies and individual insiders. It returns up to 10 ranked matches, each with name, CIK and any tickers. Words match as prefixes in any order, but abbreviations do not expand ('United States Steel', not 'US Steel'), and people are filed surname first ('Buffett Warren'). Every tool here accepts a CIK in place of a ticker, so a name match reaches a company's filings even without a ticker. The other tools take tickers directly, so call this only when you need the CIK itself or have only a name.

Input Schema

NameRequiredDescriptionDefault
nameNoInstead of 'ticker': a company, fund or person's name as filed with the SEC, e.g. 'Bridgewater Associates' or 'Buffett Warren'. Searches every EDGAR filer, with or without a ticker, and returns up to 10 ranked matches.
tickerNoStock ticker symbol, e.g. AAPL, MSFT, TSLA. A CIK (e.g. 1163302) is also accepted and returns that company's name and current tickers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Instead of 'ticker': a company, fund or person's name as filed with the\nSEC, e.g. 'Bridgewater Associates' or 'Buffett Warren'. Searches every\nEDGAR filer, with or without a ticker, and returns up to 10 ranked matches.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "ticker"
-]
  2. Changed1 schema field changedv0.7.0
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol, e.g. AAPL, MSFT, TSLA"New value: +"Stock ticker symbol, e.g. AAPL, MSFT, TSLA. A CIK (e.g. 1163302) is also\naccepted and returns that company's name and current tickers."
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

The description discloses many behavioral details beyond the read-only and open-world annotations: ticker matching is exact and case-insensitive, the ticker list is cached for an hour, unknown tickers are errors, and name search returns up to 10 ranked matches. It also explains share-class behavior and how matching works for people and abbreviations.

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?

The description is long but front-loaded and dense with operational distinctions rather than filler. Each sentence adds a matching rule, return characteristic, or routing guideline that an agent would need to invoke the tool correctly.

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 two-mode lookup tool with no output schema, the description fully covers both return shapes: a zero-padded CIK with EDGAR link for ticker lookup, and up to 10 ranked name/CIK/ticker matches for name lookup. It also covers error behavior and the CIK-as-ticker confirmation mode.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already documents both parameters at 100% coverage, the description adds substantial semantics: 'ticker' is exact and case-insensitive, accepts a CIK as a secondary mode, and 'name' searches all EDGAR filers with prefix matching in any order. These behavioral rules go well beyond the schema text.

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: looking up an SEC CIK by ticker or by name. It also distinguishes this tool from sibling tools that accept tickers directly, so an agent can tell when this lookup is needed.

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 explicitly says to call this only when the CIK itself is needed or when only a name is available, and notes that other tools take tickers directly. The two modes are clearly explained, including when to use 'name' for filers without tickers.

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

Deploy Server

Other Tools