Skip to main content
Glama

Antigravity x402 & MCP Gateway

verify_b2b_email_deliverability

[0.004000 USDC via x402] Verifies a single email or batch of up to 20 emails via RFC 5322 + IDNA normalization, role-inbox and 90+ disposable burner domain rejection, live RFC 8427 DNS-over-HTTPS MX provider classification (Google Workspace, Microsoft 365, Cloudflare, Proton, Proofpoint, Mimecast, Custom), SPF/DMARC posture, and RDAP domain registration age (< 30 days fraud flag).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify_b2b_email_deliverability"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoSingle email address to verify (e.g., 'tim@apple.com'). Provide either 'email' or 'emails'.
emailsNoBatch of 1 to 20 email addresses to verify in a single request.
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.004000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden. It discloses normalization rules, role and disposable-domain rejection, live DNS-over-HTTPS MX classification, SPF/DMARC checks, RDAP age fraud flagging, and x402 cost. It does not describe result verdicts or error behavior, but it provides substantial behavioral context.

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 description is a single dense sentence containing relevant technical capabilities, with no obvious filler. It front-loads pricing before the purpose, which is useful but slightly less direct than leading with what the tool does.

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?

The description covers purpose, inputs, and verification behavior well, but there is no output schema and it does not explain return values or error handling. For a three-parameter verification tool this is adequate, but output semantics remain incomplete.

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 description coverage is 100%, so the input schema already documents all three parameters. The description reinforces the single-vs-batch distinction and 20-email limit, but adds little beyond the schema and does not further explain the x402 payment signature.

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 description states a specific verb and resource: 'Verifies a single email or batch of up to 20 emails,' then enumerates the exact verification dimensions. This is far more specific than a name restatement and clearly identifies the tool's scope.

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 indicates single-email and batch usage with a 20-email cap and pricing, but does not explicitly say when to use this tool versus alternatives or when not to use it. Usage is implied by the purpose rather than stated as direct guidance.

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.