Proton Suite Agent

Delete an email

proton_delete_email

Destructive

Delete an email by moving it to Trash (reversible) or permanently expunging it (irreversible).

Instructions

Deletes a message. Default mode='trash' moves it to Trash (reversible). mode='permanent' expunges immediately — cannot be undone.

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": {
      "uid": "<uid>"
    },
    "name": "proton_delete_email"
  }
}

Input Schema

Name	Required	Description	Default
`uid`	Yes
`mode`	No		trash
`mailbox`	No		INBOX
`trash_path`	No	Override for the Trash mailbox path. If omitted, the \Trash special-use mailbox is auto-detected (works with Papelera/Corbeille/etc.).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.0Jul 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already indicate destructiveHint=true. Description adds that trash mode is reversible and permanent is irreversible, which is beyond annotations. No contradictions. Could mention more about side effects (e.g., attachments), but sufficient.

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?

Two sentences, front-loaded with the action, then explains modes. No unnecessary words. Highly efficient.

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

Completeness3/5

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

Covers core deletion behavior and mode distinction. But lacks context on mailbox parameter (defaults to INBOX), and does not mention authentication or response. Given no output schema, more detail on return value would help. Still, adequate for a simple delete tool.

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 low (25%). Description explains the 'mode' parameter's two values and default behavior, adding meaning. However, it does not describe 'uid', 'mailbox', or 'trash_path' beyond what schema provides. Partial compensation.

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?

Clearly states 'Deletes a message' with specific verb and resource. Distinguishes two deletion modes (trash vs permanent), which differentiates from any implicit alternative. No ambiguity.

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?

Provides guidance on when to use each mode: default is reversible trash, permanent is irreversible. However, does not explicitly mention when to use this tool over other actions (e.g., moving to trash via move). Still, the two modes are well-explained.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server