Skip to main content
Glama
richelo

isitdisposable-mcp

by richelo

Check a batch of emails and domains for disposable

check_batch
Read-only

Validate up to 100 email addresses or domains in one call, identifying disposable ones and providing recommended actions like allow, warn, or block.

Instructions

Checks up to 100 email addresses or domains at once in a single call, which is far more efficient than calling the single-item tools in a loop. Provide a mixed list in items: entries containing an @ sign are sent as email addresses, and all other entries are sent as bare domains. A disposable address is a throwaway or temporary inbox (for example from a burner mail service) that someone uses to receive a single signup message and evade normal registration requirements, rather than a real, ongoing mailbox. In the response, disposable is the core true or false verdict. action is the recommended handling: allow, warn, or block, based on the caller's own account policy. Extra opt in signals may also be present: mx_valid (whether the domain's mail servers accept mail at all), relay (a forwarding or catch all style address rather than a dedicated inbox), public_domain (a well known free provider such as Gmail or Outlook), and did_you_mean (a likely intended domain when the one given looks like a typo). This tool always fails open: if a network problem, timeout, rate limit, or server error prevents a real check, the call still succeeds and returns checked false with action allow, plus a note explaining the check could not be completed. Treat that outcome as inconclusive, never as evidence the address is safe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes1 to 100 entries, each either a full email address or a bare domain. Entries containing an @ sign are checked as email addresses; all other entries are checked as bare domains.
Behavior5/5

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

Annotations only say readOnly and openWorld. The description adds crucial behavioral details: fail-open behavior (call succeeds with checked false, action allow, note), the meaning of disposable, and the purpose of extra signals like mx_valid, relay, public_domain, and did_you_mean. No contradictions with 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 appropriately sized for a complex batch tool. Every sentence adds value: efficiency, input format, definition of disposable, response fields, and fail-open handling. Well-structured and front-loaded with the core purpose.

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?

With no output schema, the description fully covers return values and edge cases. It explains all relevant response fields, the meaning of a disposable address, and the inconclusive fail-open outcome. This is complete for the tool's complexity.

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 input schema already fully describes the 'items' parameter with 100% coverage, including the @-sign rule and min/max. The description mainly echoes this rule without adding new parameter-specific semantics, so baseline 3 applies.

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?

Clearly states the tool checks up to 100 emails or domains in a single call, with a specific verb and resource. It explicitly distinguishes from sibling tools by noting efficiency over looping single-item tools.

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?

Provides explicit guidance on when to use this tool instead of alternatives (batch vs loop), how to structure the mixed list, and how to interpret the response. Includes fail-open behavior, making it clear what to expect on errors.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/richelo/isitdisposable-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server