PersonIQ

Unlock a property report

unlock_property_report

Owner identification and resident skip trace for a property. Costs 8 credits. Returns a quote first.

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": {
      "searchId": "<searchId>",
      "propertyId": "<propertyId>"
    },
    "name": "unlock_property_report"
  }
}

Input Schema

Name	Required	Description
`format`	No	Rendering of the human-readable text channel. "prose" (default) is a compact summary an agent can reason over; "json" repeats the data verbatim; "report" is a formatted Markdown report to show a person; "html" is a standalone HTML document for saving, printing or PDF. Machine-readable structuredContent is always included either way.
`searchId`	Yes	searchId returned by search_properties.
`propertyId`	Yes	propertyId of the row to unlock.
`confirmToken`	No	Omit to receive a quote. Pass the token from that quote to start the job.

Output Schema

Name	Required	Description	Default
`data`	Yes
`apiVersion`	Yes
`disclaimer`	Yes
`balanceNotice`	No
`suggestedNext`	No
`criminalCaveat`	No
`notConsumerReport`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Adds genuinely useful context beyond the annotations: a concrete cost of 8 credits and a quote-before-charge flow, which tells the agent this is a metered operation requiring explicit user confirmation. Annotations already establish readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the remaining gap (async job retrieval) is modest.

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 short sentences with zero filler, front-loading the capability, then cost, then the confirmation protocol. Every sentence carries a distinct, decision-relevant fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the return shape need not be explained, and the credit/quote behavior is covered. However, 'start the job' implies an asynchronous job whose results must be fetched via the get_job sibling, and the description never says the unlock is deferred rather than immediate, which is a meaningful omission for a paid, non-idempotent call.

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 coverage is 100% and the properties already document searchId provenance, propertyId, the four format renderings, and the confirmToken quote handshake in detail. The description only weakly echoes the quote flow and adds no syntax, defaults, or constraints beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific action and resource (unlock a property report) and states exactly what data the unlock yields: owner identification and resident skip trace. It does not differentiate from the close sibling unlock_property_by_address, so an agent cannot tell from the description alone which of the two unlock paths to take.

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

Usage Guidelines2/5

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

'Returns a quote first' hints at the two-step protocol but restates what the confirmToken schema field already says. There is no guidance on when to use this tool versus lookup_property, unlock_property_by_address, or the search tools, and no stated prerequisites such as needing a valid searchId.

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

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