Skip to main content
Glama
jgottlieb84

agentline-mcp

by jgottlieb84

capture_email_code

Provision a temporary email address, wait for a 4-8 digit verification code, and release the address. Returns the email to paste into signup forms and the captured code.

Instructions

All-in-one email verification capture: provision an email address, wait for an incoming verification code (4-8 digits by default), release the address. Use for services that email verification codes instead of SMS.

Returns email_address (paste into the signup form) and code (the captured verification code). code is null on timeout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
local_partNo
timeoutNo
release_afterNo

Implementation Reference

  • The `capture_email_code` tool handler — provisions an email address, waits for a verification code (4-8 digits), and optionally releases the address. This is the core implementation of the tool, decorated with @mcp.tool().
    @mcp.tool()
    def capture_email_code(
        local_part: str | None = None,
        timeout: float = DEFAULT_WAIT_TIMEOUT,
        release_after: bool = True,
    ) -> dict:
        """All-in-one email verification capture: provision an email address, wait
        for an incoming verification code (4-8 digits by default), release the
        address. Use for services that email verification codes instead of SMS.
    
        Returns `email_address` (paste into the signup form) and `code` (the
        captured verification code). `code` is null on timeout.
        """
        try:
            client = _client_or_init()
            addr = client.create_email_address(local_part=local_part)
            try:
                code = client.get_email_verification_code(
                    addr.email_address,
                    timeout=_clamp_timeout(timeout),
                )
                return {
                    "email_address": addr.email_address,
                    "code": code,
                    "released": release_after,
                }
            finally:
                if release_after:
                    client.release_email_address(addr.id)
        except AgentlineError as e:
            return {"error": str(e), "status_code": e.status_code}
  • The `@mcp.tool()` decorator on `capture_email_code` registers it as an MCP tool on the FastMCP 'agentline' server.
    @mcp.tool()
  • Helper `_clamp_timeout` clamps the timeout between 1.0 and MAX_WAIT_TIMEOUT (180s), used by `capture_email_code`.
    def _clamp_timeout(timeout: float) -> float:
        return max(1.0, min(float(timeout), MAX_WAIT_TIMEOUT))
  • Helper `_client_or_init` returns a cached Agentline SDK client, used by `capture_email_code` to make API calls.
    def _client_or_init() -> Agentline:
        global _client
        if _client is None:
            _client = _build_client()
        return _client
Behavior4/5

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

Describes the full process: provision, wait for code (4-8 digits by default), release address. Explains return values and timeout behavior. No annotations, so description carries the burden and does so well.

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?

Description is fairly concise with front-loaded purpose. Could be more concise by integrating the usage guideline, but overall efficient and structured.

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?

Covers main flow and return values, but lacks details on what happens if release_after=false or how local_part is used. Also no output schema to supplement, leaving some gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description does not explicitly map parameters like local_part, timeout, release_after to the process. While parameter names are somewhat self-explanatory, the description adds minimal value beyond schema.

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?

The description clearly states 'All-in-one email verification capture' and differentiates from SMS-based verification by saying 'Use for services that email verification codes instead of SMS.' This distinguishes it from sibling tools like capture_code.

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?

Directly states 'Use for services that email verification codes instead of SMS,' providing explicit guidance on when to use this tool vs alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jgottlieb84/agentline-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server