Skip to main content
Glama

create_temp_email

Generate a disposable email address from free providers to receive verification messages and OTP codes without an API key.

Instructions

Create a temporary email address. All providers are free with no API key.

Args: provider: grabmail | catchmail | guerrillamail | maildrop username: Custom username prefix. Random if omitted.

Returns: JSON with the new address and provider name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_temp_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNograbmail
usernameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description does add real value by disclosing that every provider is free and requires no API key, which is important pre-call knowledge. However, it says nothing about the lifetime/expiry of the created address, any rate limits, or whether the address persists across calls — the most consequential behavioral facts for a 'temporary' resource.

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

Conciseness4/5

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

The core purpose is front-loaded in one sentence, followed by compact Args and Returns sections with no filler. The Returns section is mildly redundant given an output schema exists, but it costs little.

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

Completeness3/5

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

An output schema exists, so omitting return-shape detail would be acceptable, and parameter semantics are well covered. The gap is behavioral: for a two-parameter, zero-annotation creation tool, an agent still cannot tell how long the address lives or whether creation is repeatable/unlimited.

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 description coverage is 0% and the schema has no enums, so the description carries the load — and it does: it enumerates the four valid provider values (grabmail, catchmail, guerrillamail, maildrop) and explains that username is a prefix defaulting to random. That is meaningful added semantics beyond the bare string properties.

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?

The description opens with a specific verb and resource ('Create a temporary email address'), which clearly separates it from read-oriented siblings like check_email and list_temp_emails. It never names an alternative explicitly, so it stops short of the sibling-differentiation bar for a 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus check_email, list_temp_emails, or wait_for_email, nor any prerequisite or exclusion guidance. The only contextual note ('All providers are free with no API key') is about cost/auth, not about tool selection.

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