Prosp

Search prospects

search_prospects

Read-onlyIdempotent

Semantic free-text search over the companies you have already discovered. Does not run a new discovery and does not cost credits. Returns LEAN prospect SUMMARIES (domain, name, industry, size, location, employee_count, logo, a short description and a semantic_score) — not the full record. To get every field for one company (contacts, emails, registry data, social profiles, ...), call get_prospect(domain) with the summary's domain. Pagination is progressive: the response carries has_more and an opaque next_cursor; pass that cursor back to fetch the next page. When has_more is false / next_cursor is null you have seen everything above the relevance floor — stop paging.

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": {
      "query": "<query>"
    },
    "name": "search_prospects"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`cursor`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds value beyond them: zero credit cost, lean-summary payload shape, a relevance floor, and progressive cursor pagination semantics including the termination condition.

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 constraints, with zero filler sentences. The one inefficiency is enumerating the summary fields (domain, name, industry, size, ...) that the output schema already provides.

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 an output schema present, return values do not need explaining, and pagination plus the drill-down path are covered. The only real gap for a 3-parameter search tool is the undocumented `limit` (default page size and any max).

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 description coverage is 0%, so the description must carry the load. It explains `query` (semantic, free-text, over already-discovered companies) and `cursor` (opaque, pass back `next_cursor` to page), but says nothing about `limit`, which has a default of 20 and no stated meaning or bounds.

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?

Opens with a specific verb+resource+scope: 'Semantic free-text search over the companies you have already discovered.' It immediately separates itself from new-discovery siblings and from get_prospect, so an agent can pick it without opening other schemas.

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?

States what it does NOT do ('does not run a new discovery and does not cost credits') and names the exact alternative and condition: 'To get every field for one company ... call get_prospect(domain) with the summary's `domain`.' It also gives explicit stop conditions for paging via `has_more` / `next_cursor`.

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

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