Skip to main content
Glama

Start a mailbox's warmup

start_mailbox_warmup
DestructiveIdempotent

Use this when the user wants a mailbox warmed up, or a paused warmup started again. The mailbox then exchanges emails with other mailboxes on its own, under its sender name, so that mail providers come to trust it; a mailbox without a sender name is refused. Included at no charge. A Gmail mailbox that asks for an app password cannot be started here, because a password is never typed into a conversation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accountId": "<accountId>"
    },
    "name": "start_mailbox_warmup"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesThe mailbox's address, its `id` (any case, `@` as is or as `%40`).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare openWorldHint, destructiveHint, and idempotentHint, so the bar is lower, yet the description still adds real value: it explains that the mailbox sends actual emails to other mailboxes, that a sender name is a hard precondition, and that no billing applies. It does not discuss duration, volume, or how to stop the warmup once started.

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?

Three sentences, front-loaded with the usage trigger before mechanism and exclusions; little waste. 'Included at no charge' is marginal but does inform a user-facing decision.

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?

For a one-parameter mutation with no output schema, the description covers the trigger, the mechanism, the key preconditions, and one hard exclusion. Remaining gaps (what is returned, warmup duration, how to undo) are secondary but would help.

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?

With a single parameter at 100% schema coverage, the schema already explains that accountId accepts the address, `id`, any case, and `@` or `%40`. The description adds only the sender-name precondition, not any clarification of the identifier itself, so this sits at the baseline.

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 gives a specific verb and resource ('mailbox warmed up', 'paused warmup started again') and describes the mechanism (autonomous email exchange under the sender name). It implicitly distinguishes itself from pause_mailbox_warmup by covering the restart case, though it doesn't name the sibling explicitly.

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?

It states clearly when to use it: the user wants a mailbox warmed up or wants a paused warmup resumed. It also gives two exclusions (a mailbox without a sender name is refused; a Gmail mailbox needing an app password cannot be started here), but it never names where those cases should go instead.

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