Skip to main content
Glama

Edgar Ticker To Cik

edgar_ticker_to_cik
Read-onlyIdempotent

Resolve a US stock ticker (e.g. "TSLA") OR a company name (e.g. "Tesla", "Apple Inc") to the SEC's 10-digit CIK identifier — required by every other SEC tool. Call THIS FIRST when you have a ticker/name and need to use edgar_company_concept, edgar_company_filings, edgar_company_facts, sec_8k_recent, or any other SEC-keyed tool. Returns {cik, cik_padded, company_name, ticker, matched_by}; when matched by name it also returns alternatives — up to 3 OTHER companies whose names also matched, one per distinct CIK, with the winner's OWN share classes/tickers excluded (never listed as its own alternative). Use alternatives to tell a genuinely CONTESTED name match (a real rival company also matched) from a clean one (nothing else did). Cheap, no rate limit concerns. Most other tools also accept tickers/names directly and call this internally — only use it explicitly when you want the CIK as data. The response carries a next hint: the usual NEXT step after resolving is edgar_company_snapshot({ticker_or_cik}), which returns the recent filings list AND the headline XBRL financials in one call — do not chain edgar_company_filings then edgar_company_concept by hand to get that.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "AAPL"
    },
    "name": "edgar_ticker_to_cik"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerNoREQUIRED (or one of its aliases `ticker_or_cik` / `company`). Stock ticker symbol (e.g., "AAPL", "MSFT", "TSLA") or company name (e.g., "Apple", "Microsoft")
companyNoAlias for `ticker` — use it when what you have is a company NAME ("Apple Inc.") rather than a symbol. Same argument, same behaviour.
ticker_or_cikNoAlias for `ticker` — the spelling edgar_company_filings and edgar_insider_transactions use. A ticker or company name; this tool RESOLVES to a CIK, so passing a bare CIK has nothing to look up.

Output Schema

NameRequiredDescriptionDefault
cikYesCompany CIK number
tickerYesStock ticker symbol; null for a filer not on SEC's current-listed list (delisted, bankrupt, never listed) resolved by name via matched_by "edgar_entity_search"
cik_paddedYesCIK padded to 10 digits with leading zeros
company_nameYesOfficial company name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / company
      Added value: +{
      +  "description": "Alias for `ticker` — use it when what you have is a company NAME (\"Apple Inc.\") rather than a symbol. Same argument, same behaviour.",
      +  "type": "string"
      +}
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol (e.g., \"AAPL\", \"MSFT\", \"TSLA\") or company name (e.g., \"Apple\", \"Microsoft\")"New value: +"REQUIRED (or one of its aliases `ticker_or_cik` / `company`). Stock ticker symbol (e.g., \"AAPL\", \"MSFT\", \"TSLA\") or company name (e.g., \"Apple\", \"Microsoft\")"
    • addedInput schema / properties / ticker_or_cik
      Added value: +{
      +  "description": "Alias for `ticker` — the spelling edgar_company_filings and edgar_insider_transactions use. A ticker or company name; this tool RESOLVES to a CIK, so passing a bare CIK has nothing to look up.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "ticker"
      -]New value: +[]
    • changedOutput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol"New value: +"Stock ticker symbol; null for a filer not on SEC's current-listed list (delisted, bankrupt, never listed) resolved by name via matched_by \"edgar_entity_search\""
    • changedOutput schema / properties / ticker / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  2. Changed1 schema field changed
    • 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\") or company name (e.g., \"Apple\", \"Microsoft\")"
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "cik": {
      +      "description": "Company CIK number",
      +      "type": "string"
      +    },
      +    "cik_padded": {
      +      "description": "CIK padded to 10 digits with leading zeros",
      +      "type": "string"
      +    },
      +    "company_name": {
      +      "description": "Official company name",
      +      "type": "string"
      +    },
      +    "ticker": {
      +      "description": "Stock ticker symbol",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "ticker",
      +    "cik",
      +    "cik_padded",
      +    "company_name"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "ticker": "AAPL"
      +  },
      +  {
      +    "ticker": "TSLA"
      +  }
      +]
  5. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior. The description adds substantial context beyond that: return fields, the meaning of `alternatives` for contested name matches, no rate-limit concern, and a next-step hint. It does not need to repeat safety traits, though the response-shape discussion is somewhat more than a pure behavior disclosure.

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 description is front-loaded with the core purpose and usage rule, and every major clause contributes: alternatives semantics, rate-limit reassurance, and next-step guidance. It is long for a resolver and includes some chatty asides, but the structure is purposeful rather than padded.

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?

Given that an output schema exists, the description does more than enough: it explains what is returned, how to interpret `alternatives` for contested name matches, and what the usual next tool is. Combined with the schema and annotations, an agent has everything needed to invoke this correctly.

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%, and the schema already documents `ticker`, the `ticker_or_cik` alias, and the `company` alias. The description reinforces that both ticker and company name are accepted, but does not add syntax or matching-rule detail beyond the structured fields, so baseline 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?

States a specific verb and resource: resolve a US ticker or company name to the SEC 10-digit CIK. It also names the exact downstream siblings that depend on this lookup, so an agent can distinguish this resolver from company-data tools like edgar_company_concept or edgar_company_filings.

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?

Explicitly says to call this first when a CIK is needed, names the alternatives, and clarifies when NOT to call it explicitly because most other tools accept tickers/names and resolve internally. The only-use-when-you-want-the-CIK-as-data exclusion is decisive guidance.

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.