Skip to main content
Glama

Convert a stock ticker, CIK or company name to the other two

company_ticker
Read-only

Maps a US-listed stock ticker, SEC CIK number or company name fragment to the other two, with the exchange: an exact ticker or CIK, or up to 10 names matching the words you give (the names that start with it first). From the SEC's company ticker file (public domain), cached a day and trimmed before caching. Covers companies with an SEC ticker only; a name with no match is a 404, not charged. Related tools on this server, for a different need: company_br when you need to return Brazilian company data from BrasilAPI: legal name; company_fr when you need to search French companies by name or SIREN/SIRET. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "company_ticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesA ticker (AAPL), a CIK number (320193) or a name fragment of at least 3 characters (Apple)

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
sourceNo
checkedAtNo
companiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses source data, daily caching behavior, coverage limited to companies with an SEC ticker, 404 behavior for unmatched names, and pricing/payment details including x402, USDC, supported networks, and no charge for failed calls. These are meaningful behavioral traits an agent would not know from annotations alone.

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 core purpose is front-loaded and the description remains readable despite including source, caching, failure, pricing, and alternative-tool information. Some clauses, such as payment-network and caching details, are dense, but they provide relevant operational context rather than empty 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?

For a one-parameter lookup tool with an output schema, the description supplies the needed source, coverage limits, matching behavior, failure semantics, pricing model, and related-tool routing. Return value structure can be omitted because an output schema exists, so the definition is complete enough for correct invocation.

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?

The input schema already documents the single q parameter at 100% coverage, including accepted formats. The description adds useful semantics beyond the schema: name fragments match words from the query, return up to 10 names, and prioritize names starting with the query. That is valuable matching behavior, though not exhaustive syntax guidance.

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: mapping a US-listed ticker, SEC CIK, or company name fragment to the other identifiers plus exchange. It also scopes the tool to the SEC company ticker file, making it clearly distinct from sibling company lookup tools such as company_br and company_fr.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The definition gives clear context for use: exact ticker or CIK lookups, or name fragments of at least three characters returning up to 10 matches. It also names company_br and company_fr as alternatives for Brazilian and French company data. The only minor gap is that it does not explicitly frame every use/no-use condition, but the relevant routing guidance is present.

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.

Resources