Skip to main content
Glama
mailsocket

mailsocket

Official
by mailsocket
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_inbox

Create a throwaway inbox and get its id and email address to automate signup verification, then wait for the OTP or magic link to arrive.

Instructions

Create a new throwaway inbox and return its id and email address.

Use this first, before any signup flow you want to automate. Hand the
returned ``address`` to whatever form sends the verification email, then
call ``wait_for_otp`` (or ``wait_for_link``) with the returned ``id`` to
block until the code/link arrives — no polling loop needed.

Side effects: creates a new inbox resource against the live mailsocket
account tied to the API key in use (counts against the account's
inbox quota). Makes one network call to the mailsocket API
(``openWorldHint``).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so safety profile is covered. The description adds genuinely new context: quota consumption against the account, a live network call, and the return shape. It does not, however, discuss failures (quota exhaustion, auth errors) which would be the natural next addition.

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 action and return values, then the workflow, then side effects — a sensible ordering. The side-effects paragraph is slightly verbose (parenthetically restating openWorldHint), but every sentence carries usable information.

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?

With no output schema, the description correctly supplies return values (id, address) and the full orchestration flow, so an agent can chain create_inbox into wait_for_otp. The only material omission is any explanation of the 'label' parameter.

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?

The single optional 'label' parameter has 0% schema description coverage and the description never mentions it — an agent cannot tell what a label is for or whether it affects lookups. With one undocumented param, the description fails to compensate for the coverage gap, falling below the no-param baseline of 4.

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 throwaway inbox') and even names what it returns (id and email address). This is clearly distinguishable from siblings like list_inboxes, delete_inbox, and wait_for_otp without opening any schema.

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

Usage Guidelines5/5

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

Explicit sequencing guidance: 'Use this first, before any signup flow you want to automate,' plus the follow-up step naming both alternatives ('call wait_for_otp (or wait_for_link) with the returned id'). It tells the agent when to use it and what to do next, leaving nothing to inference.

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

Deploy Server

Other Tools