Crawdar Business Research

Search businesses with structured criteria

search_businesses

Read-only

Use for a quick synchronous search when target, geography, and qualification fields are already structured. Use research_businesses for a plain-language brief, or start_lead_search for durable asynchronous work.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum businesses in this response page.
`fields`	No	Business fields to retain. Website and source evidence remain available for verification.
`offset`	No	Zero-based result offset for this response page.
`output`	No	Compact minimizes tokens. Full preserves every returned field.	compact
`target`	Yes	Business type or concise target.
`geography`	Yes	City, region, country, or Worldwide.
`qualifier`	No	Optional required signals and exclusions that can be checked in public evidence.
`includeDiagnostics`	No	Include source status and explained exclusions.

Output Schema

TableJSON Schema

Name	Required	Description
`limit`	Yes	Maximum prospects requested for this page.
`offset`	Yes	Zero-based offset of this page.
`hasMore`	Yes	Whether another result page is available.
`results`	Yes
`warnings`	Yes	Limitations the agent should retain with downstream data.
`requestId`	Yes	Request identifier for support and diagnostics.
`durationMs`	No
`nextOffset`	No	Offset for the next synchronous result page, or null when complete.
`diagnostics`	No	Source status and explained candidate exclusions.
`resultCount`	Yes	Total accepted prospects before response pagination.
`returnedCount`	Yes	Prospects returned in this response page.
`schemaVersion`	Yes	Version of the result contract.
`searchedSources`	Yes	Discovery and first-party source types consulted.
`remainingFreeSearches`	No

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds behavioral context: it is synchronous, returns a page of results, supports pagination through offset/limit, and states that Website and source evidence remain available for verification. This adds practical understanding 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.

Conciseness5/5

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

The description is two sentences, front-loaded with the primary use case and immediately routing to alternatives. Every clause carries useful information; there is no filler or redundant restating of the title.

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?

Given the rich annotations (readOnlyHint, openWorldHint), a fully documented input schema, an output schema, and explicit sibling routing, the description covers everything an agent needs to decide whether to call this tool and how to invoke it correctly. Nothing critical is missing.

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 the schema fully documents every parameter and the description does not need to repeat them. The description alludes to structured criteria (target, geography, qualification fields) but adds no deeper meaning beyond the schema. With complete schema descriptions and an output schema, a baseline 3 is appropriate.

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's purpose: 'quick synchronous search' for businesses using structured criteria. It explicitly names the resource (businesses) and the mode (structured criteria), and distinguishes it from siblings by naming alternatives and their different use cases.

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?

The description explicitly says when to use this tool (when target, geography, and qualification fields are already structured) and when to use alternatives: 'Use research_businesses for a plain-language brief, or start_lead_search for durable asynchronous work.' This is an explicit routing guide with no ambiguity.

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

All Crawdar Business Research tools Inspect

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.

TDQS

A4.4/5.0

Disambiguation4/5

Most tools map to distinct lifecycle actions (start/get/cancel/refine/retry), and the descriptions make those boundaries clear. The only real overlap is between research_businesses and search_businesses, which both perform synchronous lookups but are separated by natural-language vs structured input.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern, with lead_search reused across lifecycle operations. Even explain_crawdar and sandbox_businesses fit the naming convention well.

Tool Count5/5

Nine tools is well within the appropriate range for a business-research MCP server. The count balances synchronous search, a durable async job lifecycle, sandbox testing, and self-documentation without feeling bloated.

Completeness4/5

The async lead-search lifecycle is well covered with start, get, cancel, refine, and retry, and the synchronous and sandbox search tools cover adjacent needs. However, export is mentioned in start_lead_search but not exposed as a tool, and there is no way to list existing jobs, leaving minor gaps.

Resources

Need Help?