Andru

Find likely buyers

discover_prospects

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.

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.

Changed1 schema field changedOct 23, 2026

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"
+}

First observedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the annotations (openWorldHint=true, readOnlyHint=false, destructiveHint=false) the description discloses real behavior: a run takes "up to a couple of minutes," it defaults to the product saved on the account, and it only returns companies with sourced evidence links. It omits the commercial behavior — that this is a paid call gated by a quote and a 30-minute price hold — which the schema mentions via quoteId/maxAmountCents but is significant enough to belong in the description.

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?

Four short sentences, front-loaded with the prep context ("Before outreach") and the core behavior, then latency and the evidence guarantee. The opening clause is slightly awkward grammatically but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-param, open-world, mutating-in-cost tool with no output schema, the description covers what is returned (sourced companies with evidence links) and latency, which is good. It is incomplete on the money/workflow dimension: an agent can't tell from the description that this needs a prior quote and can incur cost, and the relationship to quote/cancel_job is left for the agent to infer from the schema.

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%, so the schema already explains all 8 parameters including defaults and the idempotency/price-cap semantics. The description's only parameter-adjacent statement, "Uses the product saved on the account," restates a default the schema already documents. Baseline 3 applies; no new syntax or guidance is added.

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 gives a specific verb and resource ("finding companies with a reason to change now", "searches the web for real companies...") and states the discriminating scope: only companies with sourced, linked evidence. It never names a sibling (e.g. preview_company, batch_fit_score, assess_company_readiness) as the alternative, so the differentiation is inferred from the evidence requirement rather than stated.

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?

"use this when the person needs new companies to sell to, for example when their pipeline is thin" gives a concrete triggering condition and a scenario. It stops short of exclusions — it does not say when NOT to use it, nor point to any of the many related siblings for scoring, previews, or readiness.

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

All Andru 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.