Andru

Find likely buyers

discover_prospects

Find companies with an urgent need for your solution. Search for real-world indicators like recent hiring, funding, or expansion to target prospects ready for change.

Instructions

Before outreach, finding companies with a reason to change now: use this when the person needs new companies to sell to, for example when their pipeline is thin. Searches the web for real companies showing the problem the person's product solves right now (hiring, launches, funding, expansion) and links the page behind every piece of evidence. Uses the product saved on the account. Takes up to a couple of minutes. Only companies with sourced evidence are returned. Paid. Check the price with quote before running.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discover_prospects"
  }
}

Input Schema

Name	Required	Description
`quoteId`	No	Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes).
`industry`	No	Target industry to search within
`companyName`	No	Your company name. Defaults to the product saved on your account.
`targetMarket`	No	Target market segment (e.g., "Series A SaaS companies")
`coreCapability`	No	The single most important thing your product does — the core capability that makes customers buy
`idempotencyKey`	No	Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice.
`maxAmountCents`	No	Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged.
`productDescription`	No	What your product does and who it's for. Defaults to the product saved on your account.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.4.9Oct 24, 2026

addedInput schema / properties / idempotencyKey

Added value: +{
+  "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice.",
+  "type": "string"
+}

addedInput schema / properties / maxAmountCents

Added value: +{
+  "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged.",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / quoteId

Added value: +{
+  "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes).",
+  "type": "string"
+}

Changed3 schema fields changedv1.4.4Oct 16, 2026

changedInput schema / properties / companyName / description

Previous value: -"Your company name"New value: +"Your company name. Defaults to the product saved on your account."

changedInput schema / properties / productDescription / description

Previous value: -"What your product does and who it's for. Infer from conversation context if the user has already described their product."New value: +"What your product does and who it's for. Defaults to the product saved on your account."

removedInput schema / required

Removed value: -[
-  "companyName",
-  "productDescription"
-]

First observedv1.4.0Mar 20, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare non-read-only, open-world, non-destructive; the description goes much further by disclosing latency ('up to a couple of minutes'), cost model (paid, quote first, maxAmountCents guard), and a quality guarantee ('only companies with sourced evidence are returned' with page links). These are exactly the traits an agent needs before committing to a paid, slow call.

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 the purpose and when-to-use in the first sentence, then layers in latency, cost, and guarantees. Dense but every clause carries information; the only minor cost is that cost/payment caveats are packed at the end.

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?

With no output schema, the description still explains the return contract (only sourced-evidence companies, evidence linked to pages) and the cost/latency envelope for a slow paid operation. It could say more about result volume or shape (e.g., how many companies, fields per record), which is the remaining gap.

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 baseline is 3; the description adds value by explaining that companyName and productDescription default to the product saved on the account, which clarifies why zero parameters are required. It does not add much on industry/targetMarket/coreCapability beyond what the schema already says.

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 — searching the web for real companies showing the problem the product solves — plus the concrete signals checked (hiring, launches, funding, expansion). An agent can distinguish this from preview_company or batch_fit_score, which operate on known companies rather than discovering new ones.

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?

Gives a clear triggering condition ('needs new companies to sell to, for example when their pipeline is thin') and a prerequisite chain ('check the price with quote before running'). It does not explicitly state when NOT to use it or name a discovery alternative, so it stops just short of a 5.

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