Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

datasets_sec_companies_search

Search SEC-reporting companies by ticker, CIK, SIC, exchange, financials, filings, or insider activity to retrieve structured company profiles.

Instructions

Search the SEC companies dataset. Searches SEC-reporting companies — 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. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input 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.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses billing cost (1 credit per record, minimum 2) and explains that several filters are open EDGAR values rather than fixed enums. It does not state read-only behavior, auth requirements, rate limits, or return shape, leaving meaningful behavioral gaps.

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 front-loaded and dense with useful information: scope, data included, sort options, open-filter behavior, and billing. It wastes little space, though it redundantly repeats the sort enum already present in the schema, and the single paragraph is quite packed.

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 with no annotations and no output schema, the description covers the dataset scope, included financial/insider data, filter semantics, and billing behavior. It could be more explicit about return records and usage alternatives, but it is largely complete given the rich input schema.

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. The description adds real semantic value by identifying entity_type, sic, sic_description, exchange, and state_of_incorporation as open filters over exact EDGAR-reported values and directing agents to the matching facet for discovery. It also restates the sort enum, though that is already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "Search the SEC companies dataset." It also names the included data types (filings, financial rollups, insider activity), making the scope clear. It does not explicitly differentiate this search from sibling tools such as datasets_sec_companies_item, datasets_sec_companies_financials, or datasets_sec_companies_insider, so it stops short of a 5.

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?

Usage is implied by "Search" plus the filterable company dataset, and the description helpfully says open-filter values can be discovered via the matching facet. However, it does not explicitly say when to use this search versus retrieving a single company, financial statements, insider records, or facets, so an agent must infer the right sibling.

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