Skip to main content
Glama

Resume a mailbox

resume_mailbox
DestructiveIdempotent

Use this when the user wants a paused mailbox to send again. Campaigns that use the mailbox start sending from it again at once, so confirm with the user first. Free.

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": "resume_mailbox"
  }
}

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

A4.4/5.0
Behavior5/5

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

Annotations mark it destructive/open-world, but the description adds the crucial consequence those hints only imply: dependent campaigns resume sending immediately, so user confirmation is required. It also adds billing context ('Free'), which no structured field supplies.

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?

Three short sentences, each earning its place: trigger, side effect plus caution, cost. The action and its immediate consequence are front-loaded.

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 single-parameter action with no output schema, the description covers the effect, the confirmation requirement, and cost. It omits what happens when the mailbox is already active, though idempotentHint partly covers that.

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 description coverage is 100% and the schema already explains that accountId accepts an address or id, any case, with '@' or '%40'. The description adds nothing further about the parameter, so the baseline 3 is appropriate.

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?

The description gives a specific verb and resource ('resume a paused mailbox') and states the concrete effect ('Campaigns that use the mailbox start sending from it again at once'), which cleanly separates it from pause_mailbox and from campaign-level resume tools. An agent can act without opening the schema.

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 gives an explicit trigger ('when the user wants a paused mailbox to send again') and an operational rule ('confirm with the user first'). It does not name the inverse tool or state what to do if the mailbox is not paused, leaving a small inference gap.

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