Skip to main content
Glama
Ploid MCP

Ploid MCP

Official
by ploidcom

Get a person's email

get_email

Look up a person's work email by person_id or LinkedIn URL, then check their personal email only if no work address is found. Misses are free.

Instructions

Look up one person's email, identified by exactly one of person_id (from search_people) or linkedin_url. Tries the work email first (1 ACU when found); only when no work email exists does it look up the personal email (3 ACU when found). Misses are free. Never upgrades an existing profile: a person researched at any level is reread for free. An unresearched person starts standard research_person (10 ACU on success; deep later costs the 15 ACU difference) and returns a run_id; the work email then arrives with the completed get_research_status result (call get_email again only if that result has no work email, to try the personal one).

Input Schema

NameRequiredDescriptionDefault
person_idNoA person_id returned by search_people, up to 500 characters. Provide this or linkedin_url, not both.
linkedin_urlNoAn HTTPS LinkedIn person profile URL such as https://www.linkedin.com/in/name, up to 2048 characters. Provide this or person_id, not both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description goes well beyond by disclosing the ACU cost ladder (1 for work, 3 for personal, free misses), the work-then-personal fallback, the no-upgrade guarantee, and that an unresearched person triggers research_person and returns a run_id. The gap is that it does not state rate limits, whether triggering research is reversible/cancellable, or the shape of a successful email payload.

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 and identifier constraint, and each subsequent sentence carries distinct information (cost, fallback, no-upgrade, run_id flow) rather than filler. It is dense to the point of being hard to scan, and 'deep later costs the 15 ACU difference' is cryptic without knowing the tier pricing.

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?

There is no output schema, so the description must carry return behavior, and it does: either an email with its cost, or a run_id whose work email arrives via get_research_status. Combined with the fallback and re-call rule, an agent has everything needed to call it correctly and interpret the outcome.

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% and the schema already documents both parameters and the anyOf exclusivity, so the description's 'exactly one of' largely restates it. It does add provenance value by tying person_id to search_people output, which helps an agent know where a valid value comes from.

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 specific verb and resource ('look up one person's email') plus the exact identifying key constraint ('exactly one of person_id or linkedin_url'). It also implicitly separates itself from search_people (the source of person_id) and research_person (the fallback path), so an agent can distinguish it without opening a 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?

Explicitly names the alternatives and the conditions that select them: use search_people to obtain a person_id, use research_person for an unresearched person, and call get_email again only if get_research_status returns no work email. It also states a when-not condition (never upgrades an existing profile; a researched person is reread free).

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