Skip to main content
Glama
OpenInbox – Email for AI Agents

OpenInbox – Email for AI Agents

Official

Wait for email

wait_for_email

Waits for a matching email to arrive in an inbox, then returns its full content, including text, detected verification codes, and links, so agents can complete signups, logins, or email-flow tests.

Instructions

Wait until a matching email arrives in an inbox and return it in full (text, detected codes, links). Without "since", returns the newest unread matching email, so repeated calls return successive emails.

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

Input Schema

NameRequiredDescriptionDefault
fromNoOnly match senders containing this text.
sinceNoISO timestamp — only match emails received after it (read or unread).
subjectNoOnly match subjects containing this text.
inbox_idYesThe inbox_id returned by create_inbox.
timeout_secondsNoHow long to wait (default 60).

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?

Annotations flag openWorldHint and non-idempotency; the description reinforces this by explaining that repeated calls yield successive emails, which is exactly the behavior an agent needs to know. It also discloses the blocking wait and the returned payload, though it does not say what happens on timeout (error, null, or empty result).

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?

Two dense sentences, front-loaded with the core purpose and then the default-behavior caveat. No filler.

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?

Given no output schema, the description usefully describes return contents, and it covers the matching defaults. The remaining gap is timeout behavior — a wait tool with a 5-300s timeout should say what a caller gets when nothing arrives.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning to 'since': with it, only emails after that timestamp (read or unread); without it, the newest unread match. That clarifies default matching behavior the schema does not.

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?

States a specific verb and resource (wait until a matching email arrives and return it) plus the scope of the return payload (text, detected codes, links). It is distinct from list_emails/read_email by its blocking-until-arrival semantics, though it never names those siblings explicitly.

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?

The 'without since' sentence implicitly explains the polling use case: repeated calls return successive emails. However, there is no explicit guidance on when to use this versus list_emails or read_email, and no statement of when not to use it.

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