Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Bulk Email MX, Syntax & Disposable Verifier

verify_bulk_emails_mx_syntax
Read-onlyIdempotent

Validate email lists in bulk against RFC syntax and live DNS MX records, flag disposable providers and role accounts, and assess cold-email deliverability readiness before outreach.

Instructions

Verify email lists in bulk for RFC syntax, live DNS MX records, disposable providers, role accounts, and cold-email deliverability readiness ($0.50/1k).

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": {
      "emails": "<emails>"
    },
    "name": "verify_bulk_emails_mx_syntax"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYesEmail addresses to verify

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

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 safety is covered. The description adds genuine value beyond them by enumerating the five check categories and disclosing a per-unit cost of $0.50/1k, which lets an agent reason about expense before calling. It stops short of stating batch size limits, timeouts, or whether partial results are returned.

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?

One well-formed sentence with the primary action front-loaded and the cost signal placed at the end where it is easy to scan. The enumerated check list is dense but every item conveys a distinct verification dimension; 'cold-email deliverability readiness' is the one slightly vague phrase.

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?

The tool is simple, read-only, single-parameter, and has no output schema, and the enumeration of checks effectively tells the agent what categories of result to expect. Missing are practical operational details like maximum batch size and how per-address verdicts are reported, which matter for a bulk tool with no output schema to explain the return shape.

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?

A single parameter with 100% schema description coverage, so the schema already carries the semantics. The description reinforces that input is a list ('in bulk', 'email lists') but adds no constraints such as maximum array length, accepted format beyond RFC, or deduplication behavior. Baseline 3 applies.

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 (verify) and resource (email lists in bulk) plus the exact dimensions checked: RFC syntax, live DNS MX records, disposable providers, role accounts, and deliverability readiness. No sibling in the catalog performs email verification, so it is unambiguously distinguishable from the lead-scraping tools around it.

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?

Usage is only implied: an agent can infer this belongs after lead scraping and before outreach, but the description never says when to call it versus other tools, what prerequisites exist, or when verification is unnecessary. No exclusions or alternative-routing guidance is given.

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