Skip to main content
Glama

Leads email pattern

leads_email_pattern

Work out how a company builds its email addresses (first.last@, f.last@ …) and apply it to the staff found on its site. Says plainly whether each address is published, inferred or a guess.

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": {
      "websites": "<websites>"
    },
    "name": "leads_email_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
websitesYesCompany websites or domains (max 25).
maxPagesPerSiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description usefully discloses that results can be published, inferred, or guesses, helping prevent inferred addresses from being mistaken for confirmed ones. It also identifies the company site as the staff source, but leaves verification depth, crawl behavior, and performance or coverage limits unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences front-load the task and end with the useful distinction between published, inferred, and guessed addresses. The pattern examples and provenance information earn their space, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter tool, the core workflow and uncertainty labeling are adequately covered. With no annotations or output schema, however, the missing crawl/default behavior, verification semantics, and alternative-tool routing leave moderate gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents websites, including the 25-item cap, while maxPagesPerSite has no schema description and receives no explanation in the description. Its default, allowed range, and effect on coverage or runtime remain unspecified, and the description adds little parameter meaning beyond the schema.

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 clearly states that the tool infers a company's email-address convention and applies it to staff found on the company's site, with concrete pattern examples. It does not explicitly differentiate itself from related tools such as leads_find_contacts or email_verify.

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 wording implies use when staff email addresses must be derived from a company website, but it gives no explicit when-to-use or when-not guidance. In particular, it does not explain whether to use this before or instead of leads_find_contacts, leads_verify_domains, or email_verify.

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.

Resources