Skip to main content
Glama

Freedom Agent Mail

wait_for_email

Wait for unread email in an inbox and return it, including extracted one-time codes and verification links. Returns immediately if unread mail exists. Each message is returned once; it is marked read afterwards.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesThe inbox token returned by create_inbox.
timeout_secondsNoHow long to wait (0-60). Default 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the immediacy behavior, the once-only consumption semantics, and the destructive side effect of marking messages read. It omits what happens when the timeout elapses or the token is invalid, which is the main remaining gap for a blocking tool.

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?

Four short sentences, front-loaded with the purpose, then immediacy, then consumption semantics. Nothing is redundant and the ordering puts the most decision-relevant facts first.

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 two-parameter tool with no output schema and no annotations, the description covers purpose, blocking behavior, and the read-marking side effect. It is slightly incomplete on timeout/failure returns, which an agent calling a 0-60 second blocking operation would want to know.

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 token and timeout_seconds are already documented with ranges and defaults. The description reinforces the timing semantics but adds no format or constraint detail beyond the schema, making the baseline 3 appropriate.

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 for unread email in an inbox') and adds a distinguishing capability: extracted one-time codes and verification links. It is clearly not a plain list or read tool, though it never names read_email or list_emails to sharpen the contrast.

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 behavior 'returns immediately if unread mail exists' implies when to use it (blocking wait for a message that has not arrived yet), but there is no explicit when-to-use/when-not clause and no named alternative such as read_email or list_emails for the non-waiting case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources