Skip to main content
Glama
Ploid MCP

Ploid MCP

Official
by ploidcom

Search people by name

search_people

Find up to 10 matching profiles in Ploid's people index without starting research, then choose a candidate; narrow by name, company, location, or title.

Instructions

Find up to 10 matching profiles in Ploid's people index for 1 ACU per completed search, including no matches, without starting research. Failed searches are not charged. Results are bounded, not exhaustive, and indexed details may be stale; identity_verified is always false here (research_person verifies) and profile_url is only set for a non-LinkedIn profile. A company filter matches that employer exactly, including its aliases. Show the candidates and ask the user to choose before research_person, even for a single match. Use company, location or title to narrow a name.

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": "search_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe person's name, 2 to 200 characters.
limitNoMaximum matches to return. Whole number from 1 to 10, default 5. Values outside this range are rejected without charge.
titleNoJob title, up to 200 characters.
companyNoCurrent or past company, up to 200 characters.
locationNoCity, region or country, up to 200 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and openWorldHint=true; the description adds the actual economics and limits: 1 ACU per completed search including zero-match results, no charge on failures, bounded/non-exhaustive results, possible staleness, identity_verified always false, and profile_url only for non-LinkedIn profiles. That is exactly the kind of beyond-schema context an agent needs before spending credits.

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 the core action and capped cardinality, then cost, then caveats, then the workflow instruction. Dense but nearly every clause carries decision-relevant information; the identity_verified/profile_url sentence is compressed to the point of requiring some domain familiarity.

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 5-parameter lookup with no output schema, the description covers cost, failure charging, result bounds, staleness, field guarantees, and the required follow-up step with the user. Nothing an agent needs to invoke it safely or interpret the response 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 100%, so baseline would be 3, but the description adds real meaning: the company filter matches that employer exactly and resolves its aliases, and title/location/company are framed as narrowing filters on a name. Limit semantics are left to the schema, which already documents the 1-10 range.

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 concrete verb and resource with scope: 'Find up to 10 matching profiles in Ploid's people index ... without starting research.' The trailing clause explicitly separates it from research_person, so an agent can route 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 workflow rule — 'Show the candidates and ask the user to choose before research_person, even for a single match' — plus narrowing advice ('Use company, location or title to narrow a name'). Both a when-to-use and a when-not-to-proceed case are stated.

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