Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_sec_companies_search

Search SEC-reporting companies by name, ticker, financials, and insider activity. Filter by revenue, net income, assets, filings, and more to find target companies.

Instructions

Search the SEC companies dataset. Searches SEC-reporting companies stored in a search index — normalized filing history, financial-statement rollups (latest annual/quarterly revenue, net income, total assets) and trailing-90-day insider (Form 3/4/5) activity. Sort enum: relevance, name_asc, revenue_desc, net_income_desc, filing_recent_desc, insider_activity_desc. entity_type, sic, sic_description, exchange, and state_of_incorporation are open filters over the exact values EDGAR reports for each filer (not a fixed enum) — discover real values via the matching facet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over the company name, or an exact ticker match, max 256 characters
cikNoExact CIK filter, numeric or zero-padded, e.g. 320193 or 0000320193
sicNoExact SIC industry-code filter, e.g. 3571, max 32 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, name_asc, revenue_desc, net_income_desc, filing_recent_desc, insider_activity_desc
tickerNoExact ticker filter (case-insensitive), e.g. AAPL, max 32 characters
exchangeNoExact exchange filter as reported by EDGAR, e.g. Nasdaq, NYSE, max 64 characters
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
form_filedNoExact form-type filter; keeps only companies that have ever filed this form, e.g. 10-K, 8-K
entity_typeNoExact entity-type filter as reported by EDGAR (e.g. operating), max 64 characters
max_revenueNoMaximum latest-annual revenue in USD (normalized), 0 or greater
min_revenueNoMinimum latest-annual revenue in USD (normalized from the filer's reporting currency at reference rates), 0 or greater
has_financialsNoWhen true, keep only companies that have XBRL financial statements
min_net_incomeNoMinimum latest-annual net income in USD (normalized; negative allowed)
sic_descriptionNoExact SIC description filter, e.g. Electronic Computers, max 128 characters
min_total_assetsNoMinimum latest-annual total assets in USD (normalized), 0 or greater
reporting_currencyNoExact reporting-currency filter, ISO-4217 code, e.g. USD, JPY, EUR
state_of_incorporationNoExact state/country-of-incorporation filter as reported by EDGAR, e.g. DE, CA, max 32 characters
min_insider_txn_count_90dNoMinimum insider (Form 3/4/5) transaction count in the trailing 90 days, 0 or greater

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "name_asc",
+  "revenue_desc",
+  "net_income_desc",
+  "filing_recent_desc",
+  "insider_activity_desc"
+]
  2. Addedv1.6.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description bears the burden of behavioral disclosure. It adds useful context: several filters are open over exact EDGAR-reported values rather than a fixed enum, financial values are normalized, and insider activity is limited to a trailing 90-day window. It does not mention read-only behavior, pagination behavior, or result shape, so some behavioral traits remain undisclosed.

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 and well-structured, front-loading the dataset scope and condensing sort and filter guidance efficiently. Minor redundancy between 'Search the SEC companies dataset' and 'Searches SEC-reporting companies,' plus a sort list already present in the schema, keeps it from a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 19-parameter search tool with no output schema and no annotations, the description covers the data source, normalized metrics, sort keys, and the non-enum nature of several filters, which is enough to select and invoke the tool correctly. It omits response format and how filters combine, but those are not essential to making a valid call.

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 description coverage is 100%, so the baseline is 3. The description adds genuine value by clarifying that entity_type, sic, sic_description, exchange, and state_of_incorporation are open filters over exact EDGAR values and by directing agents to the matching facet for real values rather than a fixed enum.

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 and resource: searching SEC-reporting companies stored in a search index, with details on normalized filing history, financial-statement rollups, and trailing-90-day insider activity. The description clearly differentiates this from item-detail, financials-only, and facet siblings even without naming them.

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

Usage Guidelines3/5

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

The implied use case is searching the SEC companies dataset by query and filter criteria, and the description points to the matching facet for discovering valid filter values. However, it never names sibling alternatives or states when not to use this tool, leaving routing mostly to inference.

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

Deploy Server

Other Tools