Prosp

Get discovery status

get_discovery_status

Read-onlyIdempotent

Poll a discovery job by its jobId. Returns the lifecycle state (queued, processing, completed, failed, exhausted), total_prospects (the canonical count of validated prospects delivered so far — the SAME field name get_discovery_results carries, so you can group/count across both; prospectsFound is a deprecated alias of it) and target counts, and found: the prospect DOMAINS discovered so far — which accumulate PROGRESSIVELY while the job runs, so you see results before it finishes. For incremental polling, pass the previous response's next_cursor as cursor to receive only the domains added since your last poll (has_more stays true until the job reaches a terminal state; omit cursor to get the full list so far). Call get_prospect(domain) — or get_discovery_results once terminal — for full detail on any domain in found.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_discovery_status"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No
`job_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The annotations already establish the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add behavioral context beyond that profile. It does so: it enumerates the terminal and non-terminal lifecycle states, warns that `found` accumulates progressively so partial results appear before completion, and explains that has_more stays true until a terminal state. These details are not derivable from any structured field.

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 content is front-loaded and every clause carries information, but it is delivered as one dense paragraph with heavy parenthetical nesting (the deprecated `prospectsFound` alias, the total_prospects cross-tool note). It is not padded, but splitting it into usage, return-shape, and polling sub-statements would scan better.

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?

The tool is a polling endpoint with a two-parameter schema and an output schema already present, so return-field documentation is optional. The description still supplies the important parts: lifecycle states, the canonical count field, progressive `found` accumulation, and cursor protocol. Nothing an agent needs to poll correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 full burden. It does: cursor is defined as the previous response's next_cursor, its effect (only domains added since the last poll) and its omission semantics (full list so far) are specified, and job_id is tied to the job being polled. No parameter is left ambiguous.

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?

The description opens with a specific verb and resource: 'Poll a discovery job by its jobId.' It also distinguishes this tool from the sibling get_discovery_results, which supplies full results only once the job is terminal, and from get_prospect, which supplies per-domain detail.

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?

The description explicitly routes the agent: call get_prospect(domain) for detail on any discovered domain, or get_discovery_results once the job is terminal. It also states that polling with cursor returns only newly added domains, while omitting cursor returns the full list; this is exactly the when/when-not/alternative guidance the agent needs.

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?