SnoopScan

Find business leads

findLeads

Find businesses by what they do and where, with how to reach each one.

`who` is the trade or kind of business ("roofing contractors", "dentists"),
`where` is a town or area ("Houston, TX"). Looks on Google Maps, BBB and
Yellow Pages by default (`sources` may also name companies_house for UK
companies by trade, or web); merges duplicates; reads each business's own
website for emails, socials and a contact form (`contacts`); and with
`roles` (e.g. ["Owner"]) looks for a named person. Runs in the background
for 2 to 5 minutes: call `leadsStatus` with the job id to follow it and to
read the leads. Charged per lead delivered, never for what it cannot find.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`who`	Yes
`limit`	No
`roles`	No
`where`	Yes
`sources`	No
`contacts`	No
`requireWebsite`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: it runs in the background for 2–5 minutes, merges duplicates, reads business websites for contact info, and is charged per lead delivered. This gives the agent realistic expectations about latency, pricing, and partial success without contradicting the provided annotations.

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?

The description is dense but well-organized, front-loading the core purpose before explaining parameters and runtime behavior. Every sentence adds useful information, though the single-paragraph format could be slightly more scannable with line breaks or bullet-like separation.

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?

For a tool with seven parameters, async execution, and an output schema, the description covers the essential workflow: inputs, sources, contact enrichment, roles, background timing, and how to retrieve results. The only notable gaps are the semantics of limit and requireWebsite, but defaults and the output schema mitigate the risk.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It explains who, where, sources, contacts, and roles with concrete examples and behavior. However, limit and requireWebsite are not explained in the description, leaving two of seven parameters without semantic guidance beyond their names and defaults.

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 opens with a specific verb and resource: 'Find businesses by what they do and where, with how to reach each one.' It clearly distinguishes the tool from siblings like findContacts by emphasizing trade/location-based lead discovery plus contact enrichment, and from map/search by naming the aggregator sources and background execution.

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?

The description gives clear operational context: what inputs to provide, which sources are searched by default, how to override sources, and that results are retrieved via leadsStatus. It does not explicitly name alternatives or state when not to use this tool, but the context is strong enough for an agent to infer appropriate use.

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

All SnoopScan 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.