Skip to main content
Glama

BRAINIAC Email & Domain Intelligence

Report email deliverability checks

email-domain_deliverability-report

Combine syntax, MX, SPF, DKIM, DMARC, RDAP, and TLS checks. No message is sent, the mailbox is not checked, and a clear report does not promise delivery. Price $0.12 USDC. POST /api/v1/email-domain/deliverability-report. Unpaid calls return 402 and do not run.

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": "email-domain_deliverability-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
domainNo
selectorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely meets it: it discloses pricing ($0.12 USDC), transport (POST /api/v1/...), and payment gating (unpaid calls return 402 and do not run), plus explicit non-actions (nothing sent, mailbox not touched, no delivery guarantee). It omits latency, idempotency, and what the report actually returns, so it falls short of fully self-describing.

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?

The check list is front-loaded, then scope limits, price, endpoint, and payment behavior follow in short ordered statements. No filler; every clause carries either capability, constraint, or cost information.

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?

Cost, payment failure mode, and non-goals are covered, which is more than most descriptions offer, but for a 3-parameter composite tool with no output schema and no annotations, the definition leaves parameter contract and report contents unexplained. An agent can decide whether to pay for it, but not reliably how to fill the request.

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?

Schema description coverage is 0% and the description says nothing about any of the three parameters. It never explains whether email and domain are alternatives or complements, or that selectors are DKIM selectors (bounded to 6) — a non-obvious point an agent must infer from the mere mention of "DKIM" in the check list.

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?

"Combine syntax, MX, SPF, DKIM, DMARC, RDAP, and TLS checks" names the exact resources inspected and makes clear this is an aggregate report rather than a single-record lookup, which distinguishes it from siblings like spf-record-analyze or tls-inspect. It stops short of explicitly naming those siblings as alternatives.

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 enumerated check list implies this is the one-shot option when you want everything at once, but there is no explicit when-to-use/when-not-to-use statement versus running the individual per-check siblings. The negative scope statements (no message sent, mailbox not checked, no delivery promise) constrain interpretation of results rather than guide tool selection.

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