generect-mcp

Validate email deliverability

validate_email

Read-only

Check deliverability of emails you already have. BILLABLE — about $0.005 per email submitted — every address is billed, whatever the verdict (Tier 0 list price; your account may pay a different rate — call get_balance for your real prices, and read cost.amount_charged in every response for what was actually spent). This is the one operation where EVERY submitted address is billed — the verdict is the deliverable. Never validate an address that generate_email just returned as valid; it is already verified.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`emails`	Yes	Email addresses to validate. Each one is billed.
`timeout_ms`	No	Request timeout in milliseconds.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cost`	No
`results`	No
`submitted`	No
`test_mode`	No
`test_mode_notice`	No
`vocabulary_warnings`	No
`deprecated_params_ignored`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "cost": {
+      "additionalProperties": false,
+      "properties": {
+        "amount_charged_usd": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "billed": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "operation": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "deprecated_params_ignored": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "results": {},
+    "submitted": {
+      "type": "number"
+    },
+    "test_mode": {
+      "type": "boolean"
+    },
+    "test_mode_notice": {
+      "type": "string"
+    },
+    "vocabulary_warnings": {
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedSep 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses critical billing behavior: every address is billed regardless of result, with specific cost and how to find actual charges. It also notes that the verdict itself is the deliverable. This adds significant context beyond structured annotations.

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 description is dense but every sentence earns its place: it starts with the purpose, immediately warns about billing, provides pricing specifics and how to read costs, and includes an exclusion. It's well-structured and front-loaded with the most critical information.

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?

For a billable operation, the description covers the action, cost implications, billing exceptions, and how to retrieve real charges. With an output schema also present, the agent has everything needed to call and interpret results correctly without missing details.

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?

The schema already describes both parameters with 100% coverage ('Email addresses to validate. Each one is billed.' and 'Request timeout in milliseconds.'). The description adds pricing context but does not elaborate on the meaning of individual parameters beyond what the schema provides, so it meets the baseline.

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 clearly states the action ('Check deliverability of emails you already have') and the resource ('emails you already have'), distinguishing it from generate_email which creates emails. It's specific and unambiguous, with no tautology.

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

Usage Guidelines5/5

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

Explicitly instructs when NOT to use the tool: 'Never validate an address that generate_email just returned as valid; it is already verified.' It also references get_balance for pricing, guiding the agent on alternative actions. This is clear usage differentiation.

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

All generect-mcp 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.