Skip to main content
Glama

email_intel

Profile an email address by checking syntax, MX/SPF/DMARC records, disposable status, Gravatar existence, and breach data to assess validity and exposure risk.

Instructions

Profile an email: syntax, MX/SPF/DMARC, disposable check, Gravatar, breaches.

Breach data appears only if an HIBP key is set in HIBP_API_KEY or the local key store as hibp. Gravatar existence is checked with the privacy-preserving 404 endpoint. For a richer leaked-data exposure report use breach_check.

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": {
      "email": "<email>"
    },
    "name": "email_intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the HIBP_API_KEY / local key-store dependency that silently gates breach results, and notes Gravatar is probed via the privacy-preserving 404 endpoint. It does not mention latency, rate limits, or that results are read-only network lookups, which keeps 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.

Conciseness5/5

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

Three short sentences, front-loaded with the capability list, then the conditional caveat, then the alternative. Every sentence carries information an agent needs; nothing is redundant.

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?

No output schema and no annotations, so the description must convey what comes back, and it does by enumerating the five check categories. The main residual gap is the shape of the response and whether checks are network-bound, but for a single-parameter profiling tool this is close to complete.

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?

Only one parameter (email) with 0% schema description coverage, but the description makes its meaning unambiguous by framing the whole tool as profiling a single email address. No format or validation detail is added, but none is plausibly needed for a self-evident address field.

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 ("Profile") and resource ("an email") and enumerates exactly what is checked: syntax, MX/SPF/DMARC, disposable, Gravatar, breaches. It also names the sibling it is not (breach_check), so an agent can distinguish it 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to breach_check for a richer leaked-data exposure report, and states the precondition that breach data only appears when an HIBP key is configured. It gives clear context but does not state when this tool should be avoided entirely (e.g., non-email inputs).

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