AskRentAI

Get Prospect

get_prospect

Read-onlyIdempotent

Full detail for one prospect: contact info, lead source, status, dates.

``location`` (optional): a Rent Manager Location ID, a comma-separated
list, or ``"all"`` to run across every Location on this connection (see
``list_locations``). Blank = all Locations if the connection has several,
else its only Location. Output is labelled per Location; a Location that
can't be reached is listed as skipped. IDs (property, tenant, ...) belong
to one Location, so pass that Location when you filter by one.

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": {
      "prospect_id": "<prospect_id>"
    },
    "name": "get_prospect"
  }
}

Input Schema

Name	Required	Description	Default
`location`	No
`prospect_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / location

Added value: +{
+  "default": "",
+  "title": "Location",
+  "type": "string"
+}

First observedOct 19, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior. The description adds useful operational context: blank location means all Locations when several exist, output is labelled per Location, and unreachable Locations are listed as skipped. It does not cover not-found or error behavior for a bad prospect_id, but the added multi-location semantics are meaningful.

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 first sentence is front-loaded and identifies the tool's purpose immediately. The second paragraph is long but earns its length by explaining non-obvious location fan-out behavior, though the parenthetical and backtick-heavy style adds some density.

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?

An output schema exists, and annotations cover safety semantics, so the description need not explain return shape. It adequately covers the complex location behavior and per-Location output labelling. It is only slightly incomplete because prospect_id semantics and not-found behavior are not explicitly stated.

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 parameter meaning. It thoroughly explains the optional location parameter (Rent Manager Location ID, comma-separated list, 'all', blank default, output labelling, skipped Locations) but leaves prospect_id only implied by 'one prospect' rather than explicitly defined.

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 and resource: full detail for one prospect, with the returned fields enumerated (contact info, lead source, status, dates). The 'one prospect' scope distinguishes it from list_prospects and from analytical siblings like analyze_prospect_pipeline.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by stating it returns full detail for a single prospect, and it explains the location argument well. However, it does not explicitly say when to use this instead of list_prospects or analyze_prospect_pipeline, nor does it give exclusions or alternatives.

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

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