Skip to main content
Glama

Prospeo Find Email

prospeo_find_email
Read-onlyIdempotent

Find a person's verified work email by first name, last name and company domain, via Prospeo's person-enrichment API. Returns the email only when Prospeo actually reveals and verifies it, a masked/unrevealed guess is reported as not found rather than handed back as an address. Example: prospeo_find_email({ first_name: "Patrick", last_name: "Collison", domain: "stripe.com", _apiKey: "your-prospeo-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "stripe.com",
      "_apiKey": "your-prospeo-api-key",
      "last_name": "Collison",
      "first_name": "Patrick"
    },
    "name": "prospeo_find_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesCompany website/domain, no protocol, e.g. "stripe.com"
_apiKeyNoYour Prospeo API key (get one at app.prospeo.io/api).
last_nameYesPerson's last name, e.g. "Collison"
first_nameYesPerson's first name, e.g. "Patrick"
company_nameNoOptional company name, used if Prospeo cannot resolve from the domain alone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: a masked or unrevealed guess is reported as not found rather than returned as an address, which tells the agent how to interpret a negative result. It does not cover rate limits or credit consumption, keeping it short of a 5.

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?

Three sentences, front-loaded with purpose, then the key result-semantics caveat, then an example. The example largely duplicates the schema's example block, which is mild redundancy, but nothing else is wasted.

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 carries the burden of explaining return values and does so: an email when verified, otherwise a not-found outcome. Combined with full schema coverage and annotations, an agent has enough to call and interpret this tool; only failure modes like invalid API key or no-match reasons are unaddressed.

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 all five parameters including the optional company_name fallback. The description adds only a worked example call, which restates the schema's own example rather than adding new meaning about parameter formats or interactions.

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 (find), a specific resource (a person's verified work email), the required inputs (first name, last name, company domain), and the backing provider (Prospeo person-enrichment API). No sibling tool in the list does email lookup, so the agent can route here unambiguously.

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?

The description makes the use case clear (enriching a known person at a known company into an email) and implies the precondition that you already have name plus domain. It does not name alternatives or state when not to use it, so guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.