Skip to main content
Glama

wait_for_email

Poll a temporary email address until a new message arrives or timeout, then return extracted OTP codes, verification links, or timeout status.

Instructions

Poll until a new email arrives or timeout.

Args: address: Temp email address to watch. timeout: Max seconds to wait (default 60, max 120). poll_interval: Seconds between polls (default 5, min 3).

Returns: JSON with the new message including extracted otps[] and links[], or timeout status.

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": {
      "address": "<address>"
    },
    "name": "wait_for_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
timeoutNo
poll_intervalNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the burden and does a reasonable job: it discloses that this is a blocking poll loop, gives the hard bounds (timeout max 120, poll_interval min 3), and states the two outcomes (message found vs timeout status). It does not state whether the call blocks the agent for the full timeout, what happens if the address is invalid, or any rate-limit behavior.

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?

One front-loaded sentence states the operation, followed by tightly grouped Args and Returns blocks with no filler. Every line adds information an agent would otherwise lack.

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?

For a three-parameter polling tool with no annotations, the definition covers operation, constraints, and outcomes, and the output schema carries the return shape details. Minor gaps remain around failure modes and blocking semantics, but nothing essential for correct invocation is missing.

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%, so the description must compensate, and it does: it explains each of the three parameters, including defaults and constraints (max 120 for timeout, min 3 for poll_interval) that the schema does not express. Only the address parameter is left without any format or validity detail.

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?

"Poll until a new email arrives or timeout" pairs a specific verb (poll/wait) with a specific resource and states the termination condition, which implicitly separates it from an immediate-check sibling. It never names an alternative such as check_email, so the differentiation is structural rather than explicit.

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 implied by the semantics of waiting for an arriving message, but there is no explicit when-to-use / when-not guidance and no pointer to check_email or wait_for_sms as alternatives for non-blocking or SMS cases. An agent can infer the intent but must reason about it.

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