Skip to main content
Glama

create_signup_inbox

Generate a temporary email inbox for service signups to receive verification emails and extract codes automatically, enabling AI agents to complete registrations without human intervention.

Instructions

Create a temporary signup inbox for a target service.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
service_nameYes
ttl_minutesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of the 'create_signup_inbox' tool logic. It takes an ApiClient and input parameters to interact with the API to create a mailbox.
    async def run(
        api: ApiClient,
        service_name: str,
        ttl_minutes: int | None = None,
    ) -> dict[str, Any]:
        if not service_name or not service_name.strip():
            return tool_error("validation_error", 400, "service_name is required")
    
        if ttl_minutes is not None and ttl_minutes < 1:
            return tool_error("validation_error", 400, "ttl_minutes must be >= 1")
    
        try:
            mailbox = await api.create_mailbox(ttl_minutes=ttl_minutes)
        except ApiClientError as exc:
            return exc.to_dict()
    
        email = mailbox.get("address")
        expires_at = mailbox.get("expires_at")
        if not isinstance(email, str) or not email:
            return tool_error("invalid_response", 502, "Missing mailbox address in API response")
    
        return {
            "inbox_id": email,
            "email": email,
            "expires_at": expires_at,
            "service_name": service_name.strip(),
        }
  • Registration of the 'create_signup_inbox' tool using the FastMCP decorator. It handles API authentication and calls the implementation in 'src/uncorreotemporal_mcp/tools/create_signup_inbox.py'.
    @mcp.tool(description="Create a temporary signup inbox for a target service.")
    async def create_signup_inbox(
        service_name: str,
        ttl_minutes: int | None = None,
    ) -> dict[str, Any]:
        api_key = _get_api_key()
        if not api_key:
            return _unauthorized()
        try:
            async with ApiClient(api_key=api_key) as api:
                return await create_signup_inbox_tool.run(
                    api=api,
                    service_name=service_name,
                    ttl_minutes=ttl_minutes,
                )
Behavior2/5

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

With no annotations provided, the description carries full burden but only offers 'temporary' as behavioral context, hinting at the TTL mechanism. It fails to disclose what happens upon TTL expiration, what the output schema contains (presumably inbox credentials/address), or whether creation is idempotent.

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?

The single sentence is appropriately front-loaded with the core action. However, extreme brevity contributes to under-specification given the lack of schema descriptions and annotations. No redundancy or fluff present.

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?

While the basic purpose is covered and an output schema exists (relieving the description of return value documentation), the description remains inadequate for a tool with 0% schema coverage and complex sibling interactions. It misses critical context about parameter semantics and workflow sequencing necessary for correct agent invocation.

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%, requiring the description to compensate for both parameters. It only vaguely implies 'service_name' via 'target service' without clarifying expected format (domain name? app name?). It completely omits 'ttl_minutes', leaving the agent unaware that null represents default/forever behavior versus explicit expiration.

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 clearly states the action (Create), resource (temporary signup inbox), and scope (for a target service). It effectively distinguishes from siblings like 'extract_otp_code' or 'get_latest_email' by establishing this as the provisioning step, though it could explicitly state 'Use this first' to be perfect.

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

Usage Guidelines2/5

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

No explicit guidance on when to use versus alternatives, or prerequisites for the signup workflow. While the name 'create_signup_inbox' implies it precedes extraction tools like 'extract_otp_code', the description fails to state this relationship or mention that an output (likely an email address) is needed before proceeding to wait_for_verification_email.

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/francofuji/un-correo-temporal'

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