Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_sec_companies_search

Search SEC-reporting companies by ticker, CIK, or financial metrics, filtering by revenue, net income, insider transactions, and more.

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
Behavior4/5

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

With no annotations, the description effectively communicates the tool's behavior: it searches a search index, returns normalized financial data and insider activity, and supports sorting and open filters. No contradictions or missing critical behavioral details like destructiveness or authentication.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loaded with the core purpose, and each sentence adds meaningful detail without redundancy or fluff. It efficiently conveys complex filtering behavior in a single paragraph.

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?

Given the high parameter count and absence of output schema, the description adequately explains the overall search behavior, included data, and filter idiosyncrasies. It could mention pagination trade-offs or response format to be fully complete, but it covers the essentials well.

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%, and the description adds value by explaining that certain filters (entity_type, sic, etc.) are open filters discoverable via facets, and by enumerating sort options. This enriches understanding beyond the bare schema.

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 clearly states the tool searches the SEC companies dataset, detailing the included data types (filing history, financial rollups, insider activity) and sorting options. It distinguishes from sibling tools by mentioning facets for filter discovery, implying a complementary relationship with facets tools.

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?

It explicitly states the tool's purpose for searching SEC companies, but does not provide direct guidance on when to use this tool versus alternatives like `datasets_sec_companies_item` or `sec_company_search`. The mention of using facets for filter values offers some contextual guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server