PersonIQ

Search for a person

search_person

Find people by name, phone, email, or street address. Supports name+city+state, address+city+state, phone, and name+phone. Returns the FULL record for every match — identity, phones, emails, addresses, relatives and public financial signals — with no unlock step. Costs 3 credits per search, charged once regardless of how many people match, and REFUNDED IN FULL when the search finds nobody. If you intend to follow up with get_criminal_records, resolve the subject here as precisely as you can — full name including middle name, plus age and state — because that lookup matches on the resolved name, age and phone numbers, and does not match on location itself.

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": {
      "queryType": "<queryType>"
    },
    "name": "search_person"
  }
}

Input Schema

Name	Required	Description
`age`	No
`zip`	No
`city`	No
`phone`	No	Optional phone to strengthen a NAME search.
`query`	No	Full name, 10-digit phone number, or email address. Ignored for queryType "address" — supply `street`/`city`/`state` instead.
`state`	No	Two-letter state code.
`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`	No	Street address. Required for queryType "address".
`street2`	No
`queryType`	Yes	Which kind of identifier you are searching by.
`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.8/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing billing behavior (3 credits per search, charged once regardless of match count, fully refunded on zero results) and that no unlock step is needed for the full record. The annotations only declare open-world/read-mostly semantics; the credit and refund details are the operationally critical part and are only in the description.

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?

Front-loaded with purpose, then capabilities, then cost/refund, then the downstream-tool advice — a sensible ordering. The final sentence is long and dense, but each clause carries actionable constraints rather than 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 an 11-parameter open-world search with an output schema, the description covers what is returned, what it costs, when refunds apply, and how to chain into a sibling tool. Nothing an agent needs before invoking it is missing.

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 coverage is 64%, and the description compensates by explaining which parameter combinations are meaningful per identifier type, which the schema's flat property list does not convey. It does not address age, zip, street2, or format, leaving that portion to the schema.

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?

Opens with a specific verb and resource plus the identifier types covered: 'Find people by name, phone, email, or street address.' This clearly separates it from address-oriented siblings (lookup_property, search_properties) and phone-only siblings (reverse_phone_lookup, phone_intelligence).

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?

Enumerates the valid identifier combinations (name+city+state, address+city+state, phone, name+phone) so the agent knows which queryType shapes work. It also states an explicit follow-up relationship: resolve the subject here before get_criminal_records, and specifies the precision required (middle name, age, state) because that tool does not match on location.

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?