Skip to main content
Glama

check_email

Check a temporary email inbox and automatically extract OTP codes and verification links from new messages.

Instructions

Check inbox for new messages. Auto-extracts OTP codes and verification links.

Args: address: Temp email address to check.

Returns: JSON with messages, each containing extracted otps[] and links[].

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

Input Schema

NameRequiredDescriptionDefault
addressYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden, and it does disclose real behavior beyond the name: OTP/link auto-extraction and the shape of the payload. It does not say whether the call blocks, whether messages are consumed/marked as read, or whether an address must already exist, which matters for a mutation-adjacent inbox read.

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?

Front-loaded with the core purpose and structured with clear Args and Returns sections; every sentence is relevant. The Returns block partly duplicates the existing output schema, which is minor waste.

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 single-parameter read tool with an output schema already describing the response, the description covers purpose, extraction behavior and the parameter's meaning adequately. The remaining gap is behavioral — blocking semantics and preconditions — rather than structural.

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 0% and the schema only labels the field 'Address', so the description's clarification that it is a 'Temp email address to check' adds genuine meaning — it scopes the value to this service's disposable addresses. It stops short of specifying format or that the address must have been created first.

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?

The description gives a specific verb and resource ('Check inbox for new messages') plus a distinctive capability ('Auto-extracts OTP codes and verification links'), so the agent knows exactly what it does. It does not distinguish itself from siblings such as wait_for_email or check_paid_sms, leaving the polling-vs-blocking and free-vs-paid distinction unstated.

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 only implied: the 'Temp email address' phrasing signals this is used against an address created earlier, presumably via create_temp_email. There is no explicit when-to-use, when-not, or routing to wait_for_email for blocking behavior, so an agent must infer the choice.

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