Skip to main content
Glama

Edgar

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Edgar Companies By Sic

edgar_companies_by_sic
Read-onlyIdempotent

AUTHORITATIVE peer / competitor lookup: find every SEC filer classified under one SIC (Standard Industrial Classification) industry code. PREFER OVER WEB SEARCH for "who are $COMPANY's public competitors/peers", "list companies in ", "which filers are in SIC ". Pass EITHER sic directly (a 2-4 digit code, e.g. "3571" = Electronic Computers) OR ticker_or_cik for a company whose own SIC should be looked up first and then used to find its peers (self excluded by default). Returns each peer's CIK, and ticker + company_name when the filer has a listed ticker — results are sorted so currently-listed peers come first, since an SIC bucket covers every filer that EVER filed the form (many delisted/defunct); unlisted registrants still appear after them with ticker:null rather than being dropped. Source: SEC EDGAR company-search (browse-edgar), filtered to filers who have filed the given form_type (default "10-K", i.e. active public reporters — omitting this filter is unreliable upstream). Note: SIC is a broad, sometimes dated bucket assigned once at registration — treat this as a peer-set STARTING POINT, not a precise competitor list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikNoAlias for `ticker_or_cik` — takes a ticker or a CIK. Declared because sibling SEC tools spell this argument differently.
sicNoSIC code to search directly, e.g. "3571" (Electronic Computers), "2836" (Biological Products), "6021" (National Commercial Banks). Provide this OR ticker_or_cik.
limitNoMax peers to return (1-100, default 25).
tickerNoAlias for `ticker_or_cik` — takes a ticker or a CIK. Declared because sibling SEC tools spell this argument differently.
form_typeNoOnly include filers who have filed this form type (default "10-K" — active public reporters). SEC's upstream search is unreliable with this left blank.
exclude_selfNoWhen resolving via ticker_or_cik, exclude that company itself from the peer list. Default true.
ticker_or_cikNoTicker (e.g. "AAPL") or CIK of a company whose SIC should be resolved first, then used to find its peers. Provide this OR sic. Aliases: `cik`, `ticker`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / cik
      Added value: +{
+  "description": "Alias for `ticker_or_cik` — takes a ticker or a CIK. Declared because sibling SEC tools spell this argument differently.",
+  "type": "string"
+}
    • addedInput schema / properties / ticker
      Added value: +{
+  "description": "Alias for `ticker_or_cik` — takes a ticker or a CIK. Declared because sibling SEC tools spell this argument differently.",
+  "type": "string"
+}
    • changedInput schema / properties / ticker_or_cik / description
      Previous value: -"Ticker (e.g. \"AAPL\") or CIK of a company whose SIC should be resolved first, then used to find its peers. Provide this OR sic."New value: +"Ticker (e.g. \"AAPL\") or CIK of a company whose SIC should be resolved first, then used to find its peers. Provide this OR sic. Aliases: `cik`, `ticker`."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial behavioral context beyond that: results sorted with listed peers first, delisted/defunct filers included, unlisted registrants returned with ticker:null rather than dropped, self-exclusion default, form_type='10-K' as an active-reporter filter, and upstream unreliability without it. This is rich, honest behavioral disclosure.

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 description is dense with useful, non-redundant information and is front-loaded with purpose and usage guidance. It is longer than ideal and uses emphatic capitalization somewhat heavily, but each sentence contributes meaningful context about behavior, sources, or caveats. Slightly sprawling but earned.

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?

With no output schema, the description still covers the return shape (CIK, ticker, company_name), ordering behavior, the null-ticker case, the default form_type filter, and the reliability caveat. For a tool with 7 optional parameters and subtle behavioral quirks, nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains the resolution flow for ticker_or_cik (look up SIC first, then find peers), the consequence of exclude_self, and why form_type should not be omitted ('unreliable upstream'). This elevates the value beyond what the structured schema alone provides.

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 opens with a specific verb and resource: 'find every SEC filer classified under one SIC ... industry code.' It also positions itself as a peer/competitor lookup, which distinguishes it from sibling EDGAR tools like edgar_company_facts or edgar_search_filings. The scope (SIC-based, SEC filers) is unambiguous.

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?

It explicitly tells the agent to PREFER this tool OVER WEB SEARCH for concrete intents ('who are $COMPANY's public competitors/peers', 'list companies in <industry>'). It also explains the two input modes (sic directly vs ticker_or_cik) and warns that the SIC bucket is a starting point, not a precise list. It doesn't explicitly contrast with sibling EDGAR tools, but the primary alternative (web search) is clearly handled.

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