Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Answer a prospect search

prospects_answer

Answer the question of a search whose status is needs_input by changing its brief: ask the person, then send only the parts that change (for example more places, with their country codes). It carries on under the same hold. A search left waiting a day ends with what it found. 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": {
      "search_id": "<search_id>",
      "brief": "<brief>"
    },
    "name": "prospects_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefYesThe parts of the brief that change, in the words prospects_get shows it in (question.brief). A list replaces the whole list, so send every item it should keep; codes change facet by facet; what you leave out stays as it was.
search_idYesThe call_id prospects_find answered with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / answer
      Removed value: -{
-  "maxLength": 2000,
-  "minLength": 1,
-  "type": "string"
-}
    • addedInput schema / properties / brief
      Added value: +{
+  "additionalProperties": false,
+  "description": "The parts of the brief that change, in the words prospects_get shows it in (question.brief). A list replaces the whole list, so send every item it should keep; codes change facet by facet; what you leave out stays as it was.",
+  "minProperties": 1,
+  "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": [],
+      "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"
+    }
+  },
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "search_id",
-  "answer"
-]New value: +[
+  "search_id",
+  "brief"
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, it discloses that the search continues under the same hold, that a search left waiting a day ends with what it found, and that the operation is free. These are useful state-machine and cost details, though hold semantics and repeat-call behavior remain somewhat terse.

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 purpose and key operational detail are front-loaded with no filler. Some phrasing is compressed to the point of ambiguity, especially 'carries on under the same hold' and the one-word sentence 'Free.'

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 non-destructive mutation with a nested brief and no output schema, the description covers the essential context: when it applies, how to update, continued processing, expiry, and cost. It does not describe the response shape, but the schema carries most remaining burden.

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?

The schema already provides 100% coverage and detailed nested descriptions, including that lists replace existing lists and omitted fields stay unchanged. The description reinforces partial updates and gives a places/country-codes example, but adds little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action and resource: answering a search by changing its brief, with the precondition that its status is needs_input. That condition helps distinguish it from sibling search tools, though no sibling is explicitly named.

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?

It clearly says when to use the tool (a search whose status is needs_input) and how to proceed (ask the person, then send only changed parts). It stops short of naming alternatives or stating when not to use it.

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

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