Skip to main content
Glama

BRAINIAC Email & Domain Intelligence

Verify an email domain

email-domain_verify

Resolve a public domain and report whether nameserver, address, and MX records were found. MX presence does not mean a mailbox exists. Price $0.03 USDC. POST /api/v1/email-domain/verify. 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_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
domainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 does well on the commercial/operational side: fixed price of $0.03 USDC, the POST endpoint, and the 402-on-unpaid-call behavior with no execution. It omits any statement about what a domain that fails resolution returns or whether the two inputs can be combined.

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?

Four short sentences, front-loaded with the verb and result, then caveat, then price and endpoint. Nothing is padded; the only inefficiency is that the space saved is not spent on the parameters.

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 two-parameter tool with no output schema and no annotations, the description covers result shape at a high level ('report whether ... records were found') and covers cost/payment, but leaves the input contract wholly undocumented. Adequate to invoke, not quite adequate to invoke correctly.

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%, so the description must compensate and does not: it never mentions either the 'email' or 'domain' property, which one takes precedence, whether one is derived from the other, or that neither is required. The only hint is the word 'domain', leaving the 'email' parameter entirely unexplained.

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?

States a concrete verb and resource: resolve a public domain and report presence of nameserver, address, and MX records. That clearly distinguishes it from narrow siblings like email-domain_mx-record-check, but no sibling is named, so the differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives an interpretive caveat ('MX presence does not mean a mailbox exists') but never says when to choose this combined verify over the specific record-check or deliverability siblings. An agent must infer the routing decision from the tool name alone.

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