PersonIQ

Look up a property by address

lookup_property

Look up ONE property by street address. Use this whenever you have a specific address — do NOT use search_properties, which takes a city, ZIP or county and cannot accept an address. Returns characteristics, valuation, and distress signals (vacant, pre-foreclosure, tax delinquency, liens, owner-occupied). Owner names are masked. Costs 2 credits, charged whether or not the address matches.

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": {
      "street": "<street>"
    },
    "name": "lookup_property"
  }
}

Input Schema

Name	Required	Description
`apn`	No	Assessor parcel number. Tried before the address when supplied.
`zip`	No	ZIP code. Sufficient on its own alongside street.
`city`	No	City. Required unless zip is given.
`state`	No	Two-letter state code. Required unless zip is given.
`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.
`street`	Yes	Street address, e.g. 123 Main St.
`idempotencyKey`	No	Optional. Pass the same value when retrying a call that may have already succeeded, and you will not be charged twice.

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

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations by naming the returned data (characteristics, valuation, distress signals), disclosing that owner names are masked, and stating a cost of 2 credits charged even on a miss. The charged-on-miss caveat is exactly the kind of information the readOnly/openWorld hints cannot convey.

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?

Four short sentences, each carrying distinct information: scope, routing, output contents, privacy and cost. Front-loaded with the tool's identity and zero filler.

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 paid single-record lookup with an output schema and full parameter documentation, the description covers what is returned, what is redacted, and what it costs. Nothing needed to decide whether to call it is missing.

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%, so the baseline is 3. The description adds no detail about apn precedence, idempotencyKey, or the format enum beyond what the schema already documents, though it does reinforce the address-first input mode.

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 ('Look up ONE property by street address') and immediately distinguishes it from the sibling search_properties by describing the different input it accepts. An agent can route between the two without opening either schema.

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?

Gives an explicit positive condition ('whenever you have a specific address') and an explicit exclusion ('do NOT use search_properties, which takes a city, ZIP or county'). No inference is left to the caller.

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?