Skip to main content
Glama

Freedom Agent Mail

create_inbox

Create a new disposable email inbox. Returns its address, password and a token for the other tools. Inboxes are receive-only and are kept until deleted. Save the address and password: tokens expire, and login_inbox gets a new one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoOptional domain. Defaults to the first available domain.
usernameNoOptional part before the @. Random if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 returned credentials, the receive-only constraint, persistence until deletion, and token expiry. It omits rate limits, quotas, or whether inbox creation is metered, which is the remaining gap.

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 action and return payload, then lifecycle and credential-saving advice. No filler, and the most consequential warning (tokens expire) lands at the end where it is memorable.

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?

There is no output schema, and the description compensates by naming exactly what is returned. Lifecycle (receive-only, kept until deleted) and token renewal via login_inbox are covered; only operational limits such as rate or quota are absent.

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 both optional parameters (domain, username) and their defaults are already documented in the schema. The description adds nothing about their semantics, so the baseline of 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?

States a specific verb and resource ('Create a new disposable email inbox') and immediately characterizes what comes back (address, password, token), which makes its role as the entry point distinct from siblings like login_inbox and delete_inbox.

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?

Tells the agent to save the address and password, warns that tokens expire, and points to login_inbox as the way to obtain a new token. It stops short of explicit when-not guidance or prerequisites such as any creation quota, but the operative context is clear.

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