Skip to main content
Glama
inbox-recall

inbox-recall

by joey12725

Find people

find_people
Read-only

Resolve who someone is by looking up people by name or handle across every network, merging one person from WhatsApp, Instagram, and others into a single result with message counts per network.

Instructions

Look up people by name or handle across every network. One person on WhatsApp and Instagram shows up once, with message counts per network. Use it to resolve who someone is before filtering.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
formatNotext: compact, citation-tagged transcript (default). json: the full structured result.text
networkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower. The description still adds real behavior the annotations cannot convey: results are deduplicated across networks into a single person entity, and each carries per-network message counts. It omits result ordering and what happens when the query is ambiguous or matches nothing.

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, each earning its place: what it does, how results collapse across networks, and when to reach for it. The identifying behavior is front-loaded ahead of the usage hint.

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 no output schema, the description usefully sketches the return shape (one entry per person, per-network message counts), which is the most important missing piece. The remaining gap is pagination and limit behavior for a 4-parameter tool, but for a read-only lookup that is a minor omission.

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 only 25% (just the format enum), so the description must carry more weight. It does clarify the matching semantics of query (name or handle) and that network defaults to all networks, but it says nothing about limit or how the network array constrains scope. That is partial compensation, not full.

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?

States a specific verb and resource ("Look up people") plus the matching keys (name or handle) and the cross-network scope. The dedup behavior ("One person on WhatsApp and Instagram shows up once") makes the resource identity unambiguous, which is the key distinction from message-level siblings like search_messages. It stops short of naming an alternative outright, so it lands at 4 rather than 5.

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?

"Use it to resolve who someone is before filtering" gives a concrete use case and implies the ordering relative to message search. There is no explicit when-not or named alternative, but the workflow positioning is clear enough for an agent to choose this tool first when it lacks an identifier.

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