Skip to main content
Glama

Resolve company to SEC CIK (free)

edgar_resolve_company
Read-onlyIdempotent

Resolve US company tickers, CIKs, or name fragments to official SEC CIK numbers, tickers, and registrant names before fetching EDGAR filings or financial data.

Instructions

Resolve US company tickers, CIKs or name fragments to official SEC CIK numbers, tickers and registrant names using the SEC public ticker map (company_tickers.json). Use this first when you only need an identifier (e.g. "what is Nvidia's CIK?") or want to confirm which company a name refers to before fetching filings/facts. Next steps: edgar_list_filings for filings, edgar_get_company_facts for financial data. Behavior: HTTP GET to sec.gov (throttled to <=5 requests/s); the ticker map is cached for 6 hours. Covers SEC registrants with a listed ticker only (no delisted/private filers). RETURNS: "company_match" rows (cik zero-padded to 10 digits; match = the rule that hit: cik|ticker|name) or one COMPANY_NOT_FOUND error row per unmatched query. WHEN NOT TO USE: not for filings (edgar_list_filings) or financial values (edgar_get_company_facts); other tools already accept tickers/names directly. COST: free - direct sec.gov requests from this MCP server, no APIFY_TOKEN, no Apify billing. PARAMETERS: queries: each string is resolved independently and returns its own rows (or its own COMPANY_NOT_FOUND row), so mixed batches never fail as a whole. Precedence per query: all-digit strings are tried as a CIK first (leading zeros optional; must be in the ticker map), then an exact ticker (case-insensitive; class shares like "BRK-B" use a dash), then a case-insensitive substring of the registrant name; the first rule that matches wins and later rules are not applied. maxMatchesPerQuery caps the rows of every query, but only matters for broad name fragments (e.g. "bank") and for CIKs with several tickers (GOOG/GOOGL); raise it (max 25) to see more candidates, then pass the chosen ticker or cik to the other tools. EXAMPLE: {"queries":["NVDA","apple"]} -> {count:2, items:[{type:"company_match", cik:"0001045810", ticker:"NVDA", name:"NVIDIA CORP", match:"ticker"}, ...]}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "queries": "<queries>"
    },
    "name": "edgar_resolve_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesRequired. 1-50 strings, 1-200 chars each: a ticker ("NVDA", "BRK-B"), a CIK of 1-10 digits ("1045810" or "0001045810") or a case-insensitive registrant-name fragment ("nvidia"). Example: ["NVDA","apple","320193"]
maxMatchesPerQueryNoOptional integer 1-25, default 5. Max company_match rows returned per query (matters for name fragments and multi-ticker CIKs). Example: 10

Output Schema

NameRequiredDescriptionDefault
countYesNumber of rows returned
itemsYesResult rows; each has a "type" field (data rows or machine-readable "error" rows)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.2
    • changedInput schema / properties / maxMatchesPerQuery / description
      Previous value: -"Max rows per query for name-fragment searches (default 5)"New value: +"Optional integer 1-25, default 5. Max company_match rows returned per query (matters for name fragments and multi-ticker CIKs). Example: 10"
    • changedInput schema / properties / queries / description
      Previous value: -"1-50 tickers (\"NVDA\"), CIKs (\"1045810\" or zero-padded) or case-insensitive name fragments (\"nvidia\")"New value: +"Required. 1-50 strings, 1-200 chars each: a ticker (\"NVDA\", \"BRK-B\"), a CIK of 1-10 digits (\"1045810\" or \"0001045810\") or a case-insensitive registrant-name fragment (\"nvidia\"). Example: [\"NVDA\",\"apple\",\"320193\"]"
  2. Addedv1.2.1

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, it discloses the throttling rate (<=5 req/s), a 6-hour cache on the ticker map, coverage limits (listed-ticker SEC registrants only, no delisted/private filers), and per-query error-row isolation so batch failures don't cascade. This is exactly the extra context annotations cannot carry.

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 with the core purpose and heavily sectioned (Behavior, RETURNS, WHEN NOT TO USE, COST, PARAMETERS, EXAMPLE), so it scans well. It is long, though, and the PARAMETERS and COST sections partly restate the schema and title, adding some redundancy.

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?

Even though an output schema exists, the description sketches the return shape (company_match rows with 10-digit padded CIK and match rule, plus COMPANY_NOT_FOUND rows) and gives a worked example. Coverage limits, precedence, and failure behavior are all addressed, so nothing needed for correct invocation is missing.

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?

Schema coverage is already 100%, but the description adds non-obvious resolution semantics: all-digit strings try CIK first, then exact case-insensitive ticker (dash for class shares), then name substring, first match wins and later rules are skipped. It also explains when maxMatchesPerQuery actually matters (broad fragments, multi-ticker CIKs like GOOG/GOOGL).

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+resource+source of truth: resolve tickers/CIKs/name fragments to official SEC CIK numbers using company_tickers.json. It distinguishes itself from siblings by naming edgar_list_filings and edgar_get_company_facts as the downstream tools for filings and financial data.

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 use this first when only an identifier is needed or to confirm which company a name refers to, then routes to specific alternatives. A dedicated WHEN NOT TO USE section states it is not for filings or financial values and notes other tools accept tickers/names directly.

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