Conecto

Find prospects

prospects_find

Start a prospect search from a brief prospects_prepare made: businesses that fit and the people to reach there, with their work email checked, from public business pages. About two minutes for 50. The reply is 202 with a call_id, which is the search's id: follow it with prospects_get, or wait for the prospects.found event. The price of every prospect asked for is held; when the search ends, only the prospects found with a working email are charged and the rest of the hold comes back. Two searches at a time, and 1,000 prospects a month. The business's Conecto inboxes never write first to the people found: write to them from the business's own mailbox, with an outreach campaign (outreach_save_campaign with the search_id as prospect_search_id). Costs $0.05 per prospect found with a working email; nothing if none are found.

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": {
      "brief_token": "<brief_token>",
      "count": "<count>"
    },
    "name": "prospects_find"
  }
}

Input Schema

Name	Required	Description	Default
`count`	Yes	How many prospects to find: the count prospects_prepare proposed, or the one the person chose.
`brief_token`	Yes	The brief_token of a ready prospects_prepare.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Discloses a lot beyond annotations: async 202 + call_id, ~2 min for 50, price hold then partial charge only for verified emails, 2 concurrent searches, 1,000/month cap, and $0.05 per verified prospect with no charge if none found. None of this contradicts the openWorld/readOnly=false annotations; it enriches them.

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?

Front-loads what the search does and when it returns before pricing and limits. Dense but nearly every clause carries actionable info; slightly long with the pricing sentence appearing twice in effect (hold/settlement and per-prospect cost).

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?

For an async, cost-bearing, rate-limited tool with no output schema, the description covers invocation, polling/event alternative, billing settle-up, concurrency and monthly caps, and the required downstream outreach step—everything needed to call it correctly.

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 already 100% and the schema documents both count (10–100, prepare's proposed count) and brief_token (from a ready prospects_prepare). The description ties brief_token to the prospects_prepare workflow but adds no format or syntactic detail beyond the schema, so baseline 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?

States a specific verb and resource ('Start a prospect search') and precisely defines the output: businesses that fit, people to reach, with work emails checked, from public business pages. Clearly distinguished from siblings prospects_prepare (produces the brief) and prospects_get (retrieves results).

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?

Explicitly says to follow it with prospects_get or wait for the prospects.found event, and links to outreach_save_campaign with the search_id as prospect_search_id for the next step. Also names the constraint that Conecto inboxes never write first, routing the agent to the business mailbox workflow.

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

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