Skip to main content
Glama

MailFixture

by com.mailfixture
OverviewDiscussionsAdmin

wait_for_otp

Block until a message with an extracted OTP/verification code arrives, then return the code. The one-call answer to 'trigger signup, read the OTP, type it in'. Returns {message_id, best, candidates}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
matchNoFilter: `subject:term`, `from:term`, or `to:term`; a bare term matches the subject.
sinceNoOnly consider messages received after this RFC 3339 timestamp. Omit to accept a message that already arrived.
inbox_idYesInbox id (uuid) to watch.
timeout_secondsNoGive up after this many seconds (default 45, max 60).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations; description states it blocks but does not detail timeout behavior, error handling, or concurrency implications. Missing edge cases.

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?

Two sentences, no filler, front-loaded purpose. Could add minor usage guidance without significant bloat.

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?

Explains return shape, but lacks output schema. Missing details on timeout behavior, prerequisites (inbox existence), and error states.

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 covers all parameters with descriptions (100%). Tool description adds no extra parameter context, 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?

Clearly states verb 'block/wait' and resource 'OTP/verification code', with return type. Distinguishes from siblings like get_otp, wait_for_message.

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?

Mentions signup flow but lacks explicit when-not-to-use or alternatives. Does not differentiate from wait_for_message or get_otp.

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

All MailFixture toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources