Skip to main content
Glama

Pause a mailbox

pause_mailbox
DestructiveIdempotent

Use this when the user wants campaigns to stop sending from one mailbox for now. The mailbox stays connected and can be resumed later. 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": "pause_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

A3.9/5.0
Behavior4/5

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

The annotations already declare a non-read-only, destructive, idempotent operation confined to the account. The description adds meaningful behavioral context beyond them: the mailbox remains connected, the pause is reversible via resume, and there is no billing cost. It leaves out what happens to already-queued messages.

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 short sentences, front-loaded with the use condition and followed by the state outcome and cost. Every sentence adds information; only the terse "Free." fragment is slightly informal.

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 tool with full schema coverage and annotations, the description supplies the key facts an agent needs: scope, persistence of connection, and reversibility. Minor gap: it doesn't say how in-flight or queued emails are affected.

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?

There is a single accountId parameter with 100% schema description coverage, including accepted addressing formats, so the schema carries the parameter burden. The description adds nothing about which mailbox identifier to supply, which is acceptable at 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 states a specific verb and resource: stopping campaign sends from one mailbox, and it scopes the effect to that single mailbox. It distinguishes the action from pause_campaign by emphasizing the per-mailbox scope, though it doesn't name a 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?

"Use this when the user wants campaigns to stop sending from one mailbox for now" gives clear when-to-use context. It implies a temporary, reversible operation through "for now" and "resumed later," but it doesn't explicitly say when not to use it or name resume_mailbox as the counterpart.

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