Crawlora MCP

datasets_sec_companies_search

Read-only

Search SEC company records with normalized filing history, latest financial rollups, and 90-day insider-activity summaries. Costs 1 credit per record returned (minimum 2), so keep page_size to what you need. Filter by CIK, ticker, filing form, exchange, revenue, assets, or activity; use datasets_sec_companies_item for one record or datasets_sec_companies_facets for filter counts.

Input Schema

Name	Required	Description
`q`	No	Optional full-text query over the company name, or an exact ticker match, max 256 characters.
`cik`	No	Optional exact CIK filter, numeric or zero-padded, e.g. 320193 or 0000320193.
`sic`	No	Optional exact SIC industry-code filter, e.g. 3571, max 32 characters.
`page`	No	Result page number, 1-based, default 1; page times page_size must not exceed 10000.
`sort`	No	Optional sort order. Allowed values: relevance, name_asc, revenue_desc, net_income_desc, filing_recent_desc, insider_activity_desc. Defaults to relevance with q, otherwise name_asc.
`ticker`	No	Optional exact ticker filter (case-insensitive), e.g. AAPL, max 32 characters.
`exchange`	No	Optional exact exchange filter as reported by EDGAR, e.g. Nasdaq, NYSE, max 64 characters.
`page_size`	No	Page size, default 20, max 100; page times page_size must not exceed 10000.
`form_filed`	No	Optional exact form-type filter; keeps only companies that have ever filed this form, e.g. 10-K, 8-K, max 32 characters.
`entity_type`	No	Optional exact entity-type filter as reported by EDGAR (e.g. operating), max 64 characters.
`max_revenue`	No	Optional maximum latest-annual revenue in USD (normalized from the filer's reporting currency at reference rates), 0 or greater.
`min_revenue`	No	Optional minimum latest-annual revenue in USD (normalized from the filer's reporting currency at reference rates), 0 or greater.
`has_financials`	No	When true, keep only companies that have XBRL financial statements (a latest-annual revenue figure).
`min_net_income`	No	Optional minimum latest-annual net income in USD (normalized; negative allowed, for filtering out unprofitable companies with a value >= 0).
`sic_description`	No	Optional exact SIC description filter, e.g. Electronic Computers, max 128 characters.
`min_total_assets`	No	Optional minimum latest-annual total assets in USD (normalized from the filer's reporting currency at reference rates), 0 or greater.
`reporting_currency`	No	Optional exact reporting-currency filter, ISO-4217 code, e.g. USD, JPY, EUR, max 8 characters.
`state_of_incorporation`	No	Optional exact state/country-of-incorporation filter as reported by EDGAR, e.g. DE, CA, max 32 characters.
`min_insider_txn_count_90d`	No	Optional minimum insider (Form 3/4/5) transaction count in the trailing 90 days, 0 or greater.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavioral context beyond annotations: a cost model (1 credit per record, minimum 2) and a consumption warning about page_size, which an agent needs to invoke it responsibly.

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?

Three front-loaded sentences: purpose, cost implication, then filters plus alternatives. It is appropriately sized with no wasted text, though the filter enumeration partially duplicates the schema.

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?

An output schema exists, so return-value detail is unnecessary. The definition covers purpose, cost behavior, and sibling routing for a complex 19-parameter tool. The only minor gap is not contrasting against the financials/insider siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every one of the 19 parameters is already documented in the schema. The description summarizes the filterable fields (CIK, ticker, filing form, exchange, revenue, assets, activity) but adds no syntax or format detail beyond what the schema provides, so baseline 3 applies.

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 (Search) and resource (SEC company records), plus the payload dimensions returned (normalized filing history, financial rollups, 90-day insider-activity summaries). It explicitly names sibling tools, so an agent can distinguish it from datasets_sec_companies_item and datasets_sec_companies_facets without opening a schema.

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?

Gives explicit routing: use datasets_sec_companies_item for a single record or datasets_sec_companies_facets for filter counts, and warns to keep page_size to what's needed due to credit cost. It does not clarify when to prefer the financials/insider siblings, but the core when-to-use guidance is clear.

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

All Crawlora MCP tools Inspect

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.