Skip to main content
Glama

Edgar

by io.github.pipeworx-io
OverviewAdmin

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g., "AAPL", "MSFT", "TSLA") or company name (e.g., "Apple", "Microsoft")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikYesCompany CIK number
tickerYesStock ticker symbol
cik_paddedYesCIK padded to 10 digits with leading zeros
company_nameYesOfficial company name

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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\")"
  2. 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"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "ticker": "AAPL"
+  },
+  {
+    "ticker": "TSLA"
+  }
+]
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Description adds behavioral details beyond annotations: cheap, no rate limit concerns, return structure including alternatives for name matches. Annotations already declare read-only, idempotent, not destructive, and description is consistent.

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?

Description is compact, every sentence adds value. Core purpose is front-loaded with examples, followed by usage guidance and return info. No 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?

For a simple single-parameter tool with good annotations and an output schema, the description covers purpose, usage, relation to siblings, return structure, and cost/performance. Complete for effective agent usage.

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 coverage is 100% and already documents that the parameter accepts ticker or company name. Description reinforces this but does not add significant new semantic information beyond the schema.

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 it resolves a ticker or company name to the SEC's CIK identifier. It distinguishes itself from sibling tools by noting it is required by other SEC tools and that those tools can accept tickers/names directly.

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 instructs to call this first when needing to use other SEC-keyed tools, and only use explicitly when wanting the CIK as data. Provides clear when-to-use and when-not-to-use guidance.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources