PersonIQ

Cluster public web personas

investigate_person

Group public web results for a name into distinct candidate people, to disambiguate before unlocking. Costs 3 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": {
      "name": "<name>"
    },
    "name": "investigate_person"
  }
}

Input Schema

Name	Required	Description
`city`	No
`name`	Yes	Full name to investigate.
`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.
`xHandle`	No	X/Twitter handle.
`fbHandle`	No	Facebook handle.
`igHandle`	No	Instagram handle, with or without @.
`workplace`	No	Employer, to disambiguate common names.
`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

A3.8/5.0

Behavior3/5

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

Annotations already declare openWorldHint=true, destructiveHint=false and a non-readOnly profile; the description's main addition is the '3 credits' cost, which is genuinely useful behavioral context. It does not explain that this tool stops short of returning full persona data, nor whether results are cached or expire, leaving real gaps for a billed, open-world call.

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?

Two sentences, zero waste, with the core action front-loaded and the cost/sequencing constraint following. Nothing could be removed without losing information.

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?

With an output schema present, the description need not document return values, and annotations plus a rich input schema cover the rest. The remaining gap is pipeline context, such as what an agent should do with the candidate list next, which would help on a nine-parameter billed tool.

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 high at 89% across nine parameters, so the schema carries the burden, including the disambiguation helpers (workplace, city/state, social handles) and the idempotencyKey semantics. The description adds nothing beyond 'for a name', so the baseline 3 applies.

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?

The description uses a specific verb and output shape ('group public web results for a name into distinct candidate people'), and it positions the tool relative to sibling terminology by saying it happens 'before unlocking'. It is clear enough to separate this from search_person or get_person_intelligence, though it never names those siblings directly.

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?

'To disambiguate before unlocking' gives a concrete usage context and an implied workflow ordering, which is more than most definitions offer. It stops short of explicit exclusions (e.g., when to skip this and call reveal_persona directly), so it is not a full 5.

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?