Prosp

Run ICP

run_icp

Start a discovery from a saved ICP by its icpId (get one from list_icps or save_icp). Debits 100 credits and returns a jobId immediately; the job runs asynchronously (~5-25 min) — poll get_discovery_status, then get_discovery_results, exactly as for find_prospects. An unknown icpId is rejected and the debit is refunded.

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": {
      "icp_id": "<icp_id>"
    },
    "name": "run_icp"
  }
}

Input Schema

Name	Required	Description	Default
`icp_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations (which only declare it is not read-only, not idempotent, and open-world), the description discloses the 100-credit cost, the immediate `jobId` return, the ~5-25 minute async runtime, and the refund behavior on an unknown `icpId`. These are exactly the operational facts an agent needs before committing credits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action and followed by cost, async timing, and the polling path. No filler or restated title.

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?

An output schema exists, so return values need not be detailed, yet the description still names `jobId`. Combined with the credit cost, runtime window, polling sequence, and failure/refund semantics, an agent has everything required to invoke and follow up correctly.

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% for the single `icp_id` parameter, so the description must carry the load, and it does by telling the agent where the value comes from (`list_icps` or `save_icp`) and that invalid values are rejected with a refund. The only minor friction is the camelCase `icpId` spelling versus the schema's `icp_id`.

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: 'Start a discovery from a saved ICP by its `icpId`'. It implicitly distinguishes itself from the sibling `find_prospects` by noting the polling flow is 'exactly as for find_prospects', and from `run_circular_opportunity` by anchoring on a saved ICP.

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?

It explicitly routes the agent: obtain an `icpId` from `list_icps` or `save_icp`, then poll `get_discovery_status` and finally `get_discovery_results`. Both the precondition and the downstream sequence are named, leaving nothing to inference.

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?