Prosp

Find prospects

find_prospects

Start a B2B prospect-discovery job. Debits 100 credits and returns a jobId immediately; the job runs asynchronously (~5-25 min). Poll get_discovery_status with the jobId, then call get_discovery_results when it reaches a terminal state.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "criteria": "<criteria>"
    },
    "name": "find_prospects"
  }
}

Input Schema

Name	Required	Description	Default
`criteria`	Yes	Ideal-customer-profile criteria for a discovery job. Field names match the REST ``parameters`` object exactly (including the camelCase ``maxResults``) so this serialises straight onto the wire.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The annotations only declare readOnly=false, openWorld=true, idempotent=false, destructive=false. The description adds genuinely non-obvious behavior: a 100-credit debit, an immediate jobId return, and a ~5-25 minute asynchronous runtime with a polling protocol. The credit cost and long-running async nature are precisely the traits annotations cannot express.

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?

Three short sentences, zero filler, with the cost and async contract front-loaded before the follow-up calls. Every sentence carries actionable information.

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?

An output schema exists, so return values need not be explained, and the workflow is fully laid out. The one meaningful omission is the saturation pre-check behavior — a call can be held with a 409 and not charged unless acknowledge_low_yield is set, and the description never warns of that failure mode.

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% and the nested criteria object is documented in unusual depth (language steering, advisory company_sizes, the target_business_models role warning, acknowledge_low_yield). The description adds no parameter meaning beyond that, so the high-coverage baseline of 3 applies.

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?

"Start a B2B prospect-discovery job" names a specific verb and resource, and the async jobId/polling model distinguishes it immediately from get_discovery_results, get_discovery_status, search_prospects and run_icp. An agent can route to it without opening the schema.

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 supplies the full follow-up sequence (poll get_discovery_status with the jobId, then get_discovery_results on terminal state), which is exactly the when-to-use guidance an agent needs for an async job tool. It does not, however, state when to prefer this over run_icp or search_prospects, and gives no exclusions.

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

All Prosp 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?