Skip to main content
Glama

Email Finder

emails
Read-only

Find professional email addresses. Returns the address with its confidence (0 to 1) and verification status. An address that delivers but carries nothing of the person's surname (a first-name address such as laura@, which can be anyone's of that first name there) is owner_unconfirmed, with a note, and costs nothing: confirm whose it is before writing to it. Use to find a named person's work email at a company. To check an address you already have use email-verify; for the person's background use profiles. Cost: 2 credits, charged only when a call succeeds.

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": {
      "first_name": "<first_name>",
      "last_name": "<last_name>",
      "domain": "<domain>"
    },
    "name": "emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesCompany domain.
companyNoCompany name (optional).
last_nameYesLast name.
first_nameYesFirst name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover safety (readOnly, openWorld, non-destructive); the description adds the return contract (address plus confidence 0-1 and verification status) and a non-obvious edge case where a first-name-only address resolves as owner_unconfirmed with a note and no charge. The explicit cost model — 2 credits, charged only on success — is behavioral context no annotation or schema field supplies.

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 core purpose and the sibling routing are front-loaded and the cost note closes cleanly. The owner_unconfirmed sentence is long and parenthetical-heavy, packing the caveat, the note, the billing, and the recommendation into one dense clause, which costs some readability.

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?

With no output schema, the description still covers what comes back (address, confidence, verification status), the degenerate result case, and the billing rule. For a four-parameter, non-destructive lookup with annotations already declaring safety, nothing an agent needs in order to call it correctly is missing.

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 every parameter is already documented in the schema. The description implies the first_name/last_name/domain combination via "a named person's work email at a company" but adds nothing about the optional company parameter or input format expectations. Baseline 3 is appropriate when the schema carries parameter meaning.

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?

The opening sentence gives a specific verb and resource ("Find professional email addresses") and the follow-up scopes it to "a named person's work email at a company," which separates it from email-verify and profiles by name. An agent can pick this tool without opening the 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?

It states the positive case (find a named person's work email at a company) and two explicit exclusions with the alternatives named: email-verify for an address you already have, profiles for the person's background. It even routes the agent on the owner_unconfirmed outcome: confirm whose it is before writing to it.

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.