Skip to main content
Glama

Edgar

by io.github.pipeworx-io
OverviewAdmin

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
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).
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.

Schema Changelog

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

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only and idempotent behavior, but the description adds substantial detail: results are sorted with currently-listed peers first, unlisted filers appear with ticker:null, the default form_type is '10-K', and the source is SEC EDGAR browse-edgar. It also discloses that SIC buckets include delisted/defunct filers, managing expectations beyond the annotations.

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 long but well-structured: purpose is front-loaded, followed by usage guidance, parameter behavior, and caveats. Every sentence adds information, though the density makes it slightly heavier than the leanest possible definition.

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 compensates by specifying return fields (CIK, ticker, company_name), ordering behavior, and how unlisted registrants are represented. It also covers defaults, source, and limitations, so an agent has everything needed to invoke the tool correctly.

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 meaningful semantics: it clarifies that sic and ticker_or_cik are mutually exclusive alternatives and explains the ticker_or_cik lookup flow (resolve SIC first, then find peers). It also surfaces the default form_type behavior and the exclude_self default, which adds value beyond the schema's individual parameter descriptions.

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: 'AUTHORITATIVE peer / competitor lookup: find every SEC filer classified under one SIC.' It clearly distinguishes this from the many sibling EDGAR tools by framing it as the peer/competitor lookup, not a filings, facts, or holdings tool.

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?

It explicitly states when to prefer this tool over web search, with concrete example queries like 'who are $COMPANY's public competitors/peers'. It also explains the two invocation modes (direct SIC vs ticker/CIK resolution) and adds a caution that SIC is a broad starting point, not a precise competitor list.

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