Skip to main content
Glama

BRAINIAC Email & Domain Intelligence

Validate email syntax

email-domain_syntax-validate

Check that an address is a bare email with a public domain. The mailbox is not contacted, and a valid result does not mean the address exists. Price $0.01 USDC. POST /api/v1/email-domain/syntax-validate. Unpaid calls return 402 and do not run.

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-domain_syntax-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses that no mailbox contact occurs (i.e. no side effects on the target), that success is syntactic only, the $0.01 USDC cost, and the 402 failure mode where unpaid calls do not run. Only the return payload shape and any rate/quotient limits are left unsaid.

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?

Four short sentences, front-loaded with what is checked, then the key caveat, then cost and endpoint, then the payment failure mode. No sentence is redundant given the absence of annotations.

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?

For a one-parameter, no-output-schema validation tool this covers purpose, cost, transport, and failure behavior. The one genuine gap is that the shape of a 'valid/invalid' response is never hinted at, which matters since no output schema exists to fall back on.

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?

Schema coverage is 0% and the single parameter is an unconstrained string, but the description supplies the missing semantics: the value must be a bare email (no display name) and the domain must be public. That is meaningful constraint information the schema does not carry; only length/format details are absent.

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 specific verb+resource ('Check that an address is a bare email with a public domain') and scopes it tightly with two constraints: bare address only, public domain only. 'The mailbox is not contacted' implicitly separates it from the deliverability/verify siblings, though it never names them explicitly.

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: this is the cheap, offline syntax gate, and 'a valid result does not mean the address exists' hints it should not be used as a final validity check. There is no explicit 'use this before X' or 'use email-domain_verify instead when...' statement, so the agent must infer the position in the workflow.

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