Skip to main content
Glama

Pause a mailbox's warmup

pause_mailbox_warmup
DestructiveIdempotent

Use this when the user wants to stop warming a mailbox up for now. Its warmup is paused and can be started again later. A mailbox whose warmup never started is refused. 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_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
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds genuinely useful context by stating the pause is reversible ("can be started again later"), that a never-started warmup is rejected, and that the call is "Free." It does not explain side effects on in-progress sends or quota, so the added disclosure is real but partial.

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?

Four short sentences, each carrying a distinct fact: trigger condition, resulting state, precondition failure, and cost. The trigger is front-loaded and nothing is redundant.

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 state-changing tool with annotations and no output schema, the definition covers trigger, reversibility, and failure case adequately. Only minor gaps remain, such as whether related warmup metrics or schedules are affected.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter and the schema documents it fully (address or id, case-insensitive, '@' or '%40'), so coverage is 100%. The description adds nothing about the identifier, which is acceptable given a baseline of 4 for a fully covered single-parameter tool.

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 names a specific verb+resource combination ("stop warming a mailbox up for now" / "Its warmup is paused") that an agent can distinguish from starting or resuming warmup. It stops short of explicitly differentiating from the close-by sibling pause_mailbox, so an agent must infer that this targets the warmup process specifically rather than the mailbox itself.

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 explicit when-to-use framing ("Use this when the user wants to stop warming a mailbox up for now") and a clear negative precondition ("A mailbox whose warmup never started is refused"). It does not name an alternative tool such as resume_mailbox or start_mailbox_warmup, so routing is only partly spelled out.

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