Conecto

Prepare a prospect search

prospects_prepare

Read-onlyIdempotent

Check a prospect search's brief and price it, before prospects_find. You run the interview: from what the person asked for and what you know about the business, write who to find, where, and the codes from the lists. Ask the person only when what the business sells or wants is too unclear to pick any customers: one short question with choices, about the market or the kind of customer, never job titles, and never about what they already said. Conecto checks the brief, fills the defaults (20 prospects, a working email, small and medium-sized businesses) and answers with the summary, the brief as the search will run it and a brief_token. Show the person the summary, the places, the count and what it can cost (count x $0.05), and start it with prospects_find once they agree. Only accounts that have topped up search. Free.

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": {
      "request": "<request>",
      "about_us": "<about_us>",
      "brief": "<brief>"
    },
    "name": "prospects_prepare"
  }
}

Input Schema

Name	Required	Description
`brief`	Yes	Who to find, written from what the person asked for and what you know about the business.
`count`	No	How many prospects the person wants; 20 when they named no number.
`request`	Yes	What the person asked for, in their words: who, how many, where.
`website`	No	The business's website; the account's own when left out.
`about_us`	Yes	What the business sells, to whom and where, and what it wants from these prospects, from what you know about it. Don't ask the person this.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 9, 2026

changedInput schema / properties / about_us / description

Previous value: -"What the business sells, to whom and where, and what it wants from these prospects, from what you know about it. The interview never asks the person this."New value: +"What the business sells, to whom and where, and what it wants from these prospects, from what you know about it. Don't ask the person this."

removedInput schema / properties / answers

Removed value: -{
-  "additionalProperties": {
-    "anyOf": [
-      {
-        "maxLength": 300,
-        "type": "string"
-      },
-      {
-        "items": {
-          "maxLength": 300,
-          "type": "string"
-        },
-        "maxItems": 8,
-        "type": "array"
-      }
-    ]
-  },
-  "description": "The answers so far, by question id: a choice's value, several values for a multiple choice, or the person's own words.",
-  "maxProperties": 12,
-  "type": "object"
-}

addedInput schema / properties / brief

Added value: +{
+  "additionalProperties": false,
+  "description": "Who to find, written from what the person asked for and what you know about the business.",
+  "properties": {
+    "codes": {
+      "additionalProperties": false,
+      "description": "The brief in the codes Conecto's index files businesses under, from fixed lists. Codes only for what the person wants; leave out what doesn't matter.",
+      "properties": {
+        "business_model": {
+          "description": "Only when the person said how the businesses work, e.g. ecommerce.",
+          "items": {
+            "enum": [
+              "saas",
+              "manufacturer",
+              "retailer",
+              "wholesaler",
+              "distributor",
+              "marketplace",
+              "agency",
+              "consultancy",
+              "service_provider",
+              "ecommerce"
+            ],
+            "type": "string"
+          },
+          "maxItems": 10,
+          "type": "array",
+          "uniqueItems": true
+        },
+        "country": {
+          "description": "The ISO 3166-1 code of every country in places, e.g. AT for \"Vienna, Austria\". Empty only when places is.",
+          "items": {
+            "pattern": "^[A-Z]{2}$",
+            "type": "string"
+          },
+          "maxItems": 10,
+          "type": "array",
+          "uniqueItems": true
+        },
+        "customer_type": {
+          "description": "Only when the person said whom the businesses sell to.",
+          "items": {
+            "enum": [
+              "b2b",
+              "b2c",
+              "b2g"
+            ],
+            "type": "string"
+          },
+          "maxItems": 10,
+          "type": "array",
+          "uniqueItems": true
+        },
+        "department": {
+          "description": "Only for roles the person named.",
+          "items": {
+            "enum": [
+              "executive",
+              "sales",
+              "marketing",
+              "customer_success",
+              "customer_support",
+              "operations",
+              "procurement",
+              "finance",
+              "hr",
+              "engineering",
+              "it",
+              "security",
+              "product",
+              "legal",
+              "research",
+              "logistics",
+              "production"
+            ],
+            "type": "string"
+          },
+          "maxItems": 10,
+          "type": "array",
+          "uniqueItems": true
+        },
+        "employee_range": {
+          "description": "Only for a headcount the person asked for.",
+          "items": {
+            "enum": [
+              "1_10",
+              "11_50",
+              "51_200",
+              "201_500",
+              "501_1000",
+              "1001_5000",
+              "5001_10000",
+              "10001_plus"
+            ],
+            "type": "string"
+          },
+          "maxItems": 10,
+          "type": "array",
+          "uniqueItems": true
+        },
+        "industry": {
+          "description": "The most specific industries of the businesses to find (what they do, not who their customers are); a broad parent such as healthcare when nothing narrower fits. At least one.",
+          "items": {
+            "enum": [
+              "technology",
+              "technology.software",
+              "technology.cybersecurity",
+              "technology.it_services",
+              "technology.hardware",
+              "technology.telecommunications",
+              "technology.semiconductors",
+              "manufacturing",
+              "manufacturing.industrial_equipment",
+              "manufacturing.automotive",
+              "manufacturing.aerospace",
+              "manufacturing.electronics",
+              "manufacturing.chemicals",
+              "manufacturing.packaging",
+              "manufacturing.textiles",
+              "manufacturing.food_production",
+              "manufacturing.consumer_goods",
+              "retail",
+              "retail.apparel",
+              "retail.beauty",
+              "retail.home_goods",
+              "retail.grocery",
+              "retail.consumer_electronics",
+              "retail.general_retail",
+              "professional_services",
+              "professional_services.consulting",
+              "professional_services.marketing_advertising",
+              "professional_services.legal",
+              "professional_services.accounting",
+              "professional_services.recruitment",
+              "professional_services.design",
+              "professional_services.engineering_services",
+              "financial_services",
+              "financial_services.banking",
+              "financial_services.insurance",
+              "financial_services.investment",
+              "financial_services.payments",
+              "financial_services.lending",
+              "healthcare",
+              "healthcare.care_providers",
+              "healthcare.medical_devices",
+              "healthcare.pharmaceuticals",
+              "healthcare.biotechnology",
+              "healthcare.wellness",
+              "real_estate_construction",
+              "real_estate_construction.construction",
+              "real_estate_construction.property_services",
+              "real_estate_construction.architecture",
+              "real_estate_construction.building_materials",
+              "transport_logistics",
+              "transport_logistics.freight",
+              "transport_logistics.warehousing",
+              "transport_logistics.passenger_transport",
+              "transport_logistics.delivery",
+              "hospitality_travel",
+              "hospitality_travel.accommodation",
+              "hospitality_travel.restaurants",
+              "hospitality_travel.travel_services",
+              "hospitality_travel.events",
+              "media_entertainment",
+              "media_entertainment.publishing",
+              "media_entertainment.broadcasting",
+              "media_entertainment.gaming",
+              "media_entertainment.film_music",
+              "media_entertainment.sports",
+              "education",
+              "education.schools",
+              "education.higher_education",
+              "education.training",
+              "energy_utilities",
+              "energy_utilities.renewables",
+              "energy_utilities.oil_gas",
+              "energy_utilities.utilities",
+              "energy_utilities.environmental_services",
+              "agriculture_resources",
+              "agriculture_resources.agriculture",
+              "agriculture_resources.forestry",
+              "agriculture_resources.mining",
+              "public_nonprofit",
+              "public_nonprofit.government",
+              "public_nonprofit.nonprofit",
+              "public_nonprofit.associations"
+            ],
+            "type": "string"
+          },
+          "maxItems": 10,
+          "type": "array",
+          "uniqueItems": true
+        },
+        "seniority": {
+          "description": "Only for roles the person named.",
+          "items": {
+            "enum": [
+              "owner_founder",
+              "c_suite",
+              "vp",
+              "head",
+              "director",
+              "manager",
+              "individual_contributor",
+              "intern"
+            ],
+            "type": "string"
+          },
+          "maxItems": 10,
+          "type": "array",
+          "uniqueItems": true
+        }
+      },
+      "required": [
+        "industry",
+        "country"
+      ],
+      "type": "object"
+    },
+    "contact_details": {
+      "description": "What every prospect must come with; email when left out.",
+      "items": {
+        "enum": [
+          "email",
+          "phone"
+        ],
+        "type": "string"
+      },
+      "maxItems": 2,
+      "minItems": 1,
+      "type": "array",
+      "uniqueItems": true
+    },
+    "customers": {
+      "description": "Who to find: one kind of business that would itself use what the business sells, and what makes one a fit, e.g. \"independent bakeries with their own shops\". Keep the person's words when they name the businesses; when they don't, pick the most promising one from what you know about the business, never a broad pair like \"SaaS and e-commerce\". Businesses, not job titles.",
+      "maxLength": 1200,
+      "minLength": 10,
+      "type": "string"
+    },
+    "goal": {
+      "description": "What the person wants from them, e.g. first meetings with kitchens replacing old equipment.",
+      "maxLength": 1200,
+      "type": "string"
+    },
+    "industries": {
+      "description": "Those businesses' industries, in words.",
+      "items": {
+        "maxLength": 240,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 20,
+      "type": "array"
+    },
+    "leave_out": {
+      "description": "Businesses, or kinds of business, to leave out.",
+      "items": {
+        "maxLength": 300,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 30,
+      "type": "array"
+    },
+    "must_have": {
+      "description": "What every business found must be or have, only as the person stated it. No roles, contact details or counts.",
+      "items": {
+        "maxLength": 300,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 30,
+      "type": "array"
+    },
+    "offering": {
+      "description": "What the business sells them.",
+      "maxLength": 1200,
+      "type": "string"
+    },
+    "people": {
+      "description": "Roles the person asked for themselves, e.g. \"owner or head chef\"; leave it out otherwise. The search finds the right people from the goal, in every language: never ask the person to choose job titles.",
+      "maxLength": 700,
+      "type": "string"
+    },
+    "places": {
+      "description": "The market: countries, regions or cities, e.g. \"Vienna, Austria\". A local search finds named people with working emails, a worldwide one rarely does: when the person gave none, pick the business's most likely market and say so. Empty only when they ask for anywhere in the world.",
+      "items": {
+        "maxLength": 160,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 40,
+      "type": "array"
+    },
+    "sizes": {
+      "description": "Company sizes, only as the person wants them; no headcount cutoffs of your own. Left out means small and medium-sized businesses; an empty list means any size. Large companies only when asked for.",
+      "items": {
+        "maxLength": 240,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 10,
+      "type": "array"
+    }
+  },
+  "required": [
+    "customers",
+    "places",
+    "codes"
+  ],
+  "type": "object"
+}

addedInput schema / properties / count

Added value: +{
+  "description": "How many prospects the person wants; 20 when they named no number.",
+  "maximum": 100,
+  "minimum": 10,
+  "type": "integer"
+}

changedInput schema / required

Previous value: -[
-  "request",
-  "about_us"
-]New value: +[
+  "request",
+  "about_us",
+  "brief"
+]

First observedOct 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description adds real context beyond them: the defaults Conecto applies (20 prospects, a working email, SMBs), the returned summary plus brief_token, the cost formula (count x $0.05), that the call is free, and the top-up prerequisite. None of that is recoverable from the annotation block.

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-loaded with the core action and the sibling it precedes, then flows into how to run the interview and what to do afterwards; every sentence carries a rule. It is long for a single paragraph, and the conversational framing around Conecto adds a little padding, but nothing is genuinely dispensable.

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?

This is a complex tool with a deeply nested 5-parameter schema and no output schema, and the description covers the return shape (summary, the brief as it will run, brief_token), the pricing to communicate, the defaults, and the handoff to prospects_find. Nothing an agent needs to call it correctly and act on the result is missing.

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 coverage is 100%, so the schema carries the field-level burden, but the description still adds decision guidance the schema cannot: how to derive customers and places when the person named none, that codes must come from the fixed lists for what the person wants only, and the default of 20 prospects. It stops short of explaining every nested code family, which is reasonable given the schema already does.

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 — check a prospect search's brief and price it — and explicitly positions it as a prerequisite to prospects_find, which it names as the follow-up tool. An agent can distinguish this from prospects_find without opening either schema.

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?

Gives explicit sequencing (run this before prospects_find, then start the search once the person agrees), explicit exclusions for the clarifying question (only when the business or customer kind is too unclear, never job titles, never about what they already said), and an account prerequisite (only accounts that have topped up search). The alternatives and their trigger conditions are named rather than implied.

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?