Skip to main content
Glama
OpenInbox – Email for AI Agents

OpenInbox – Email for AI Agents

Official

Get verification code or link

get_verification

Waits for the next verification email in an inbox and returns just the one-time code or verification link, so agents can finish signups and logins without parsing HTML.

Instructions

Wait for the next verification email in an inbox and return just the one-time code and/or the verification / magic / password-reset link. The fastest way to finish a signup or login. Waits up to timeout_seconds for the email to arrive.

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": "get_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoOnly match senders containing this text, e.g. "github.com". Recommended when the inbox gets other mail.
inbox_idYesThe inbox_id returned by create_inbox.
timeout_secondsNoHow long to wait for the email (default 60).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses the blocking wait and that only the extracted code/link is returned, which is real added value. The significant remaining gap is that readOnlyHint=false and idempotentHint=false are unexplained: the description never says whether the matched email is consumed/marked read, or what happens on timeout when no email arrives.

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?

Three short sentences, front-loaded with the action and return value, then the use case, then the wait behavior. Every sentence carries distinct information and there is no 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 correctly fills the gap by stating exactly what is returned. For a non-idempotent, open-world blocking call it should still say what the agent gets on timeout and whether the email is consumed, which leaves a small but real hole.

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 coverage is 100%, so all three parameters are already documented, including the from-sender filter and the 5-300s timeout bounds. The description reinforces timeout_seconds and inbox scoping but adds no semantics beyond the schema, 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?

Names a specific action (wait for the next verification email) and a precise output contract (just the one-time code and/or verification/magic/password-reset link). The output-extraction framing implicitly separates it from the generic email-listing siblings without needing to name them.

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

Usage Guidelines4/5

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

"The fastest way to finish a signup or login" gives a clear situational context for reaching for this tool over list_emails/read_email. It stops short of any explicit exclusion or named alternative (e.g. when to use wait_for_email instead), so it is clear context without routing rules.

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