Crawdar Business Research

Research businesses from a brief

research_businesses

Read-only

Use for a quick synchronous search when the user supplies one natural-language brief and can wait for results in the current tool call. For durable progress, retry, export, or large agent workflows, use start_lead_search instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`brief`	Yes	Example: Independent veterinary clinics in Berlin with an active first-party website. Exclude directories and chains.
`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
`geography`	No	Optional explicit geography. Use when the brief does not make location clear.
`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

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedAug 26, 2026

addedInput schema / properties / fields / description

Added value: +"Business fields to retain. Website and source evidence remain available for verification."

addedOutput schema / properties / diagnostics / description

Added value: +"Source status and explained candidate exclusions."

addedOutput schema / properties / hasMore / description

Added value: +"Whether another result page is available."

addedOutput schema / properties / limit / description

Added value: +"Maximum prospects requested for this page."

addedOutput schema / properties / nextOffset / description

Added value: +"Offset for the next synchronous result page, or null when complete."

addedOutput schema / properties / offset / description
```
Added value: +"Zero-based offset of this page."
```

addedOutput schema / properties / requestId / description

Added value: +"Request identifier for support and diagnostics."

addedOutput schema / properties / resultCount / description

Added value: +"Total accepted prospects before response pagination."

addedOutput schema / properties / returnedCount / description
```
Added value: +"Prospects returned in this response page."
```
addedOutput schema / properties / schemaVersion / description
```
Added value: +"Version of the result contract."
```

addedOutput schema / properties / searchedSources / description

Added value: +"Discovery and first-party source types consulted."

addedOutput schema / properties / warnings / description

Added value: +"Limitations the agent should retain with downstream data."

Changed5 schema fields changedAug 26, 2026

addedOutput schema / properties / results / items / properties / contactRoute
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```

addedOutput schema / properties / results / items / properties / criteria

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / prospectStatus
```
Added value: +{
+  "enum": [
+    "qualified",
+    "possible"
+  ]
+}
```

addedOutput schema / properties / results / items / properties / whyMatch

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "prospectStatus",
+  "whyMatch",
+  "criteria",
+  "contactRoute"
+]

AddedAug 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the synchronous, quick nature and the contrast with the durable asynchronous sibling, which is valuable context beyond the annotations. It does not contradict annotations and provides the expected call-time behavior.

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?

Two sentences with zero waste. The primary use case is front-loaded in the first sentence, and the alternative is clearly stated in the second. It is concise, structured, and every word contributes to the agent's decision.

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 tool's complexity (7 parameters, 1 required) and the presence of a detailed input schema and output schema, the description is sufficient. It explains the synchronous nature and the routing to the async sibling. It does not cover pagination or output details, but those are already in the schema, and the description provides the key decision guidance for an agent.

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 coverage is 100% and all seven parameters have detailed descriptions (e.g., brief example, limit bounds, fields enum). The description does not add parameter-specific semantics but reinforces that the brief is a natural-language query. With full schema coverage, a baseline of 3 is appropriate; the description adds no extra meaning beyond the 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 states a specific verb ('research') and resource ('businesses'), and immediately defines the scope: a quick synchronous search from a natural-language brief. It distinguishes itself from start_lead_search by naming the alternative, making it clear this tool is for immediate results in the current call. No ambiguity.

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 'Use for a quick synchronous search when the user supplies one natural-language brief and can wait for results in the current tool call' and then explicitly routes other workflows ('durable progress, retry, export, or large agent workflows') to start_lead_search instead. This gives both when-to-use and when-not-to-use guidance with a named alternative.

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

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.

Resources

Need Help?