Skip to main content
Glama

Edgar

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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 for disambiguation. 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.

Input Schema

TableJSON 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

TableJSON 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.9/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, so the bar is lower, but the description adds meaningful behavioral detail beyond annotations: cheap to call with no rate limit concerns, returns a structured result including `alternatives` for name matches, and carries a `next` hint pointing to edgar_company_snapshot. No contradiction with annotations.

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 longer than average, but each part earns its place: purpose, call-order guidance, return shape, explicit-use caveat, and follow-up hint. It is front-loaded with the primary purpose and the call-first instruction, then layers in progressively finer details without repetition.

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 the tool's moderate complexity, the rich annotations, and the presence of an output schema, the description is complete enough for correct invocation. It covers aliases, when to avoid explicit use, cost/rate-limit characteristics, return shape, and even the recommended next step, leaving no practical gap for an agent.

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 description coverage is 100%, so baseline is 3, but the description adds value by explaining alias semantics (`ticker`, `company`, `ticker_or_cik`), giving concrete examples (AAPL, TSLA), and clarifying the edge case that passing a bare CIK has nothing to look up because this tool resolves to a CIK.

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 clearly states a specific verb and resource: 'Resolve a US stock ticker OR a company name to the SEC's 10-digit CIK identifier'. It also names the downstream SEC tools that depend on this resolution, distinguishing this tool from siblings like edgar_company_filings and edgar_company_concept.

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?

The description gives explicit when-to-use guidance ('Call THIS FIRST when you have a ticker/name and need to use ...') and equally explicit when-not-to-use guidance ('only use it explicitly when you want the CIK as data'). It also notes that most other tools accept tickers/names directly and call this internally, which prevents unnecessary chaining.

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

All Edgar toolsInspect
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