Skip to main content
Glama
Bosco Labs Data

Bosco Labs Data

Official

SEC company lookup: ticker to CIK (free)

find_sec_company
Read-only

Turn a ticker, CIK or company name into official SEC EDGAR data: CIK, ticker, exchange, SIC industry and state of incorporation. Use it to get the CIK that SEC filing tools require.

Instructions

Free, no API token needed. Identify a US-listed (SEC-registered) company: CIK, official name, ticker(s), exchange(s), industry (SIC code) and state of incorporation (source: SEC EDGAR company tickers file and submissions API). Use it to turn a ticker or name into the CIK that SEC tools take, or to check which exchange a stock trades on.

Pass a ticker, a CIK or part of the name (best matches first, then by company size; check
`name`). A name search covers companies with a listed ticker (about 10,000); a CIK also
finds filers without one.

Returns one row per company: cik, name, tickers, exchanges, sic, sic_description,
state_of_incorporation, fiscal_year_end (MMDD), source_url (the EDGAR company page; cite
it) and next_steps (the paid Bosco Labs calls for its filings and insider trades).

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": {
      "query": "<query>"
    },
    "name": "find_sec_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA ticker (AAPL), a CIK (320193) or part of the company name ("apple")
max_resultsNoMax companies for a name search (1-5).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.5

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses cost and auth (free, no API token), the underlying data sources (EDGAR company tickers file, submissions API), result ordering (best matches first, then by company size), and a field format (fiscal_year_end as MMDD) plus a citation instruction. That is substantive behavioral context the annotations cannot convey.

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 cost and purpose, then matching rules, then return shape. Most sentences earn their place, though the closing next_steps pitch for the paid Bosco Labs calls is mildly promotional and the field list partly duplicates the output schema.

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?

Covers lookup inputs, ranking behavior, coverage limits, output field formats, and result-source citation. With an output schema present, enumerating fields is arguably redundant, but the added format and citation details make it complete for a two-parameter lookup tool.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning: it explains that query accepts a partial name and that results are ranked by match quality then size, and that max_results only bounds name searches (consistent with the schema). It clarifies how the parameters behave rather than restating them.

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 (identify a US-listed SEC-registered company) and enumerates the returned attributes (CIK, name, ticker, exchange, SIC, state of incorporation). It explicitly positions itself as the ticker/name-to-CIK bridge for other SEC tools, which distinguishes it from search_sec_filings and search_sec_insider_trades siblings.

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?

Gives concrete when-to-use cases: convert a ticker or name into a CIK that other SEC tools require, or verify which exchange a stock trades on. It also discloses the coverage rule (name search hits ~10,000 listed companies; a CIK lookup reaches filers without a ticker). No explicit when-not or named alternatives, so it stops short of a 5.

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