Skip to main content
Glama
Ploid MCP

Ploid MCP

Official
by ploidcom

Find people

find_people

Build a verified list of people from a natural-language sales or research query, with each match checked against your criteria. Returns a resumable run_id for tracking results.

Instructions

Build a verified list of people from a natural-language sales or research query. Each match is checked against criteria derived from the query. count must be 1 to 25; other values are rejected without starting a job. Returns a resumable run_id; use get_research_status for the list.

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": {
      "query": "<query>"
    },
    "name": "find_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoPeople to find. Whole number from 1 to 25, default 10. Values outside this range are rejected without charge.
queryYesNatural-language description of the people to find, up to 4000 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (which only declare non-read-only and open-world), the description discloses that each match is checked against query-derived criteria, that count values outside 1-25 are rejected without starting a job, and that the result is a resumable run_id. It does not explain credit costs, latency, or exactly what 'verified' entails, but it adds substantial behavioral context.

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?

The description is front-loaded and concise, with the core purpose first and operational constraints after. The count range partially repeats the schema, which is a minor redundancy but also clarifies the rejection behavior.

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?

For an asynchronous, two-parameter job tool with no output schema, the description covers the essential call semantics: what it does, input limits, validation behavior, and how to retrieve results. It could be more complete by explaining the verification criteria or whether the job costs credits, but it is sufficient to invoke correctly.

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 schema already documents both parameters. The description reinforces the count range and adds that the query is natural-language sales or research criteria, but most parameter details are duplicated from the schema rather than expanding on it.

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 gives a concrete verb and resource ('Build a verified list of people') and clearly frames it as query-driven research. It explicitly distinguishes itself from get_research_status, but does not distinguish itself from the other people-finding siblings such as find_decision_makers or search_people.

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

Usage Guidelines3/5

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

It states the asynchronous flow ('Returns a resumable run_id; use get_research_status for the list') and gives a range constraint. However, it offers no guidance on when to choose this tool over sibling people-search tools, leaving that inference to the agent.

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