Crawdar Business Research

Test the Crawdar contract

sandbox_businesses

Read-onlyIdempotent

Return deterministic fictional businesses without consuming provider capacity. Use this to test schemas, clients, and agent loops.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`target`	No	Fictional business type echoed into deterministic test results.
`geography`	No	Fictional location echoed into deterministic test results.

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.

Changed13 schema fields changedAug 26, 2026

addedInput schema / properties / geography / description

Added value: +"Fictional location echoed into deterministic test results."

addedInput schema / properties / target / description

Added value: +"Fictional business type echoed into deterministic test results."

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 22, 2026

TDQS

A5/5.0

Behavior5/5

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

The description clearly indicates the tool returns fictional deterministic data and has no provider-side consumption, aligning with the readOnlyHint annotation. It also implies idempotency through 'deterministic' and is consistent with the destructiveHint false annotation. No behavioral contradictions are present.

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 tightly written in two sentences with no redundant wording. It front-loads the primary purpose and immediately follows with concrete usage guidance.

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 annotations, input schema, output schema, and sibling tool context, the description covers all essential information an agent needs: purpose, behavior, parameters, and safe usage. There are no missing critical details.

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

Parameters5/5

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

Both parameters are described with their meaning and role in generating deterministic test results. The schema coverage is 100%, and the description adds that values are 'echoed' into results, clarifying how the parameters affect output.

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 uses a specific verb ('Return') and clearly identifies the resource as deterministic fictional businesses. It also distinguishes this tool from production data tools by noting it does not consume provider capacity and is intended for testing schemas, clients, and agent loops.

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 states when to use the tool: 'Use this to test schemas, clients, and agent loops.' This provides clear guidance on the intended scenario and helps differentiate it from the sibling search/research tools.

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?