Conecto

Check email addresses

email_verify

Read-onlyIdempotent

Whether each address can take mail: deliverable, undeliverable, risky (a disposable provider, or a domain that accepts every address) or unknown, with the checks behind it (syntax, mail servers, disposable or free provider, shared mailbox, and the mailbox itself, asked of its mail server without sending anything). Up to 50 at a time. The business's Conecto inboxes never write first to an address checked here. $0.005 per address with a verdict; unknown is free. Costs $0.005 per address with a verdict; nothing if none are found.

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": {
      "emails": "<emails>"
    },
    "name": "email_verify"
  }
}

Input Schema

Name	Required	Description	Default
`emails`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the actual checks performed, that the mailbox probe is done 'without sending anything,' and the batch limit of 50. It also adds pricing per address and that 'unknown' is free, which the annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The verdict taxonomy is front-loaded and earns its space, but the pricing information is stated twice in near-identical sentences ('$0.005 per address with a verdict; unknown is free' vs 'Costs $0.005 per address with a verdict; nothing if none are found'), which is visible padding.

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?

With no output schema, the description carries the return burden and does so by naming all four verdict values plus the underlying checks. Only the per-address response shape (e.g., which check flagged a result) is left unspecified, which is a minor gap for a lookup tool.

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?

Schema description coverage is 0%, so the description must compensate; it does explain the 50-item cap ('Up to 50 at a time'), but says nothing about the string format or 254-char limit that the schema itself constrains. Adequate but thin for a single-parameter tool.

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?

States a specific verb and resource (verifying whether each address can take mail) and enumerates the exact verdict taxonomy (deliverable, undeliverable, risky, unknown), which no sibling tool duplicates. An agent can tell instantly what this returns.

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 via 'the business's Conecto inboxes never write first to an address checked here,' hinting at pre-send hygiene. There is no explicit when-to-use/when-not-to-use versus alternatives such as email_send or prospects_find, leaving the agent to infer the workflow.

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

All Conecto 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?