Crypto, web, finance and app data tools

Email Address Validation

email_validate

Check an email address before sending: syntax, whether the domain exists and has mail servers (MX), disposable/temporary provider, role address (info@, sales@), free provider and typo suggestion (gmial.com -> gmail.com), with a verdict. No mail is sent and the mailbox is not probed.

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_validate"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A4.5/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 burden, and it does meaningful work: 'No mail is sent and the mailbox is not probed' pre-empts the two most likely agent misgivings about a validation call. It does not disclose latency or that DNS/MX lookups occur over the network, which is a minor remaining gap.

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?

A single sentence, front-loaded with the imperative and the timing cue, with every clause adding a distinct check rather than restating the title. Nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return structure need not be described; 'with a verdict' is sufficient signal that a pass/fail judgement is returned. For a one-parameter read-only validation tool, the description covers everything an agent needs before calling.

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?

One parameter at 0% schema description coverage, so the description must compensate. It implies the input is a raw email address and its typo example ('gmial.com -> gmail.com') hints at accepting unnormalized input, but it does not state format expectations or whether display-name forms like 'Name <a@b.com>' are tolerated.

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?

Specific verb ('check') plus resource ('an email address') followed by an exhaustive enumeration of the checks performed: syntax, MX/domain existence, disposable providers, role addresses, free providers, typo suggestion, and a final verdict. This enumeration makes it plainly distinct from the nearest sibling, email_security, without needing to name it.

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

Usage Guidelines4/5

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

'Check an email address before sending' supplies a concrete usage trigger, which is more than most definitions offer. It stops short of explicit exclusions or naming the sibling email_security as the alternative for SPF/DMARC-style checks, so an agent must infer that boundary from the listed checks.

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

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?