Prosp

Save ICP

save_icp

Save a reusable ICP (Ideal Customer Profile) from an optional display name plus discovery criteria (same shape as find_prospects). Returns the stored ICP with a server-assigned icpId you can later pass to run_icp. Saving does NOT run a discovery and does not cost credits.

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": "<icp>"
    },
    "name": "save_icp"
  }
}

Input Schema

Name	Required	Description	Default
`icp`	Yes	Body to create a saved ICP (Ideal Customer Profile) — an optional display name plus the discovery criteria it re-runs. Mirrors the openapi ``IcpRequest`` schema field-for-field (``additionalProperties: false``, ``required: [criteria]``) so it serialises straight onto the wire. The nested ``criteria`` reuses :class:`DiscoveryCriteria`, so a saved ICP is validated by the SAME single-source schema an inline discovery is — no divergent copy.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false with destructiveHint=false; the description adds materially useful context beyond them: no discovery execution, zero credit cost, and a server-assigned icpId in the response. It does not address idempotency (annotations say idempotentHint=false), so an agent isn't told whether re-saving the same name creates a duplicate.

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 with the core action and the credit/cost caveat front-loaded, followed by the return contract. Nothing redundant and nothing padded.

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?

For a single nested-parameter write tool with annotations covering the safety profile and an output schema covering the return shape, the description supplies what remains: purpose, absence of cost, and where the icpId goes next. No gap an agent needs before calling it correctly.

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% and every field of the nested criteria object is already documented in-schema, so the parameter bar is met by the schema itself. The description's only added meaning is the 'same shape as find_prospects' equivalence and the optionality of name, which the criteria schema largely repeats.

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+resource ('Save a reusable ICP') and immediately defines it as an optional display name plus discovery criteria, explicitly equated to the shape used by find_prospects. This lets an agent distinguish it from siblings like run_icp (executes) and list_icps (enumerates) without opening any schema.

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 the key routing rule: 'Saving does NOT run a discovery and does not cost credits,' which separates it from run_icp/find_prospects, and names run_icp as the downstream consumer of the returned icpId. It stops short of stating when an agent should prefer saving an ICP over running an inline discovery repeatedly.

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?