Crawdar Business Research
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| research_businessesA | 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. |
| search_businessesA | 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. |
| sandbox_businessesA | Return deterministic fictional businesses without consuming provider capacity. Use this to test schemas, clients, and agent loops. |
| start_lead_searchA | Use for the recommended durable asynchronous workflow. Creates a private queued search job and returns a job id plus jobToken for progress polling, cursor paging, refinement, retry, cancellation, and CSV or JSON export. |
| get_lead_searchA | Read job status or one cursor-paginated result page. Keep jobToken private and pass nextCursor back unchanged. |
| refine_lead_searchA | Create a new private search job by changing the brief or criteria of a completed job. The original job stays unchanged. |
| retry_lead_searchA | Create a replacement job when a prior job failed or exceeded its execution window. The original job stays available for audit. |
| cancel_lead_searchA | Cancel a queued or running search job. Completed and failed jobs remain immutable. |
| explain_crawdarA | Get result semantics, limits, interface URLs, and safe operating guidance. This tool does not consume a search. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have clear, distinct purposes: synchronous vs asynchronous search, sandbox, and explain. The overlap between research_businesses and search_businesses is somewhat subtle but resolved by the explicit distinction between natural-language briefs and structured criteria.
All tool names follow a consistent snake_case action_object pattern (research_businesses, start_lead_search, cancel_lead_search), making their behavior predictable. Even explain_crawdar fits the convention.
Nine tools is well-scoped for a business-research service: it covers synchronous search, async job lifecycle, sandbox testing, and explanatory metadata without excess or redundancy.
The tool surface covers the full search workflow—immediate sync queries, durable async jobs, refinement, retry, cancellation, status/result reading, and safe testing—plus an explain tool for interface guidance. No obvious gaps remain.