Skip to main content
Glama
Atomic-Mail

Atomic Mail Agentic

Official
by Atomic-Mail
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Register an Atomic Mail inbox

register
Idempotent

Register a new Atomic Mail inbox with proof-of-work signup. Creates credentials and returns inbox, accountId, and apiKey on first signup. Ask your operator for the username and watch setting before calling.

Instructions

PoW signup; writes credentials. Usernames are 5–21 characters. Idempotent for the same username and stored inbox. To register another account alongside an existing one, pass credentials_dir with a separate path. Returns inbox, accountId, apiKey (first signup only). The watch value is your operator's decision, not the agent's — ask them before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
watchYesWhether a recurring job is set up to read this inbox unattended. A standing commitment on your operator's machine, so it is their decision — ask them; do not choose or infer it. The two values are "scheduled" and "on-demand"; what each one means is in help topic cron. Omit it and the call returns the requirement.
forcedNoDanger: replacing an account's credentials is irreversible and permanently destroys access to the current inbox. Operator-authorised only; the refusal error explains the safe path instead (a separate credential directory).
usernameYesPermanent public address: the local-part of your @atomicmail.ai address, 5–21 characters. It appears on every message this inbox sends and cannot be changed afterwards — if your operator has not named it, ask them rather than inventing one.
credentials_dirNoCredential directory for this call (default: ATOMIC_MAIL_CREDENTIALS_DIR or ~/.atomicmail). Use separate paths per account; see help topic multi_account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Discloses that it writes credentials, is idempotent only under a stated condition, returns account data only on first signup, and that forced replacement permanently destroys access. It also flags the watch value as requiring operator decision, adding depth beyond the annotations (idempotentHint=true, destructiveHint=false).

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?

Compact and front-loaded. Each sentence adds behavioral or usage information: idempotency condition, multi-account setup, return value caveat, and operator-authorization requirement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Considering the schema carries full parameter documentation and annotations cover idempotency, the description covers the crucial extra context: what is returned, the first-signup caveat, the destructive forced flag, and the rule to defer watch decisions to the operator.

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% with rich parameter descriptions already. The description adds a useful usage note about separate credential directories, but mostly re-states what the schema says rather than adding new meaning.

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?

Opens with a specific verb and resource ('PoW signup; writes credentials') and clarifies the exact effect (registering an Atomic Mail inbox). The idempotency condition and multi-account behavior further pin down what the tool does.

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?

Gives concrete usage guidance: idempotent for the same username and stored inbox, use a separate credentials_dir for multiple accounts, and ask the operator before deciding the watch value. It does not name sibling tools or explicitly say when not to use it, but the guidance is sufficient.

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