Skip to main content
Glama
Sign In
Proton Suite Agent

Proton Suite Agent

by Soluciones-Alexendros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Move an email to another mailbox

proton_move_email

Move a specific email from one mailbox to another by providing its UID and target folder.

Instructions

Moves a message by UID from one mailbox to another. Use proton_list_folders to see valid targets.

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": {
      "from_mailbox": "<from_mailbox>",
      "uid": "<uid>",
      "to_mailbox": "<to_mailbox>"
    },
    "name": "proton_move_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
to_mailboxYes
from_mailboxYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate mutability (readOnlyHint=false) and non-destructiveness. The description adds that it uses UID and moves between mailboxes, and hints at a prerequisite (list_folders), providing additional behavioral context beyond annotations.

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, no filler. The main action is front-loaded, and every word serves a purpose. Ideal conciseness.

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?

Given the tool's simplicity (3 params, no output schema), the description covers the core operation and links to a related tool. It does not explain return values, but this is a minor gap for a basic move command.

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?

The description does not detail each parameter beyond what the names imply, and schema coverage is 0%. However, it mentions 'by UID from one mailbox to another,' which clarifies the three parameters' roles. With three self-explanatory names, this is adequate but could provide more guidance on format or validation.

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 states 'Moves a message by UID from one mailbox to another,' which is a specific verb+resource with clear scope. It distinguishes from siblings like proton_delete_email and proton_drive_move by explicitly mentioning UID and mailbox context.

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?

The description tells when to use the tool and references proton_list_folders for valid targets, providing context. It does not explicitly mention when not to use or direct alternatives, but the purpose is clear enough for an agent to decide.

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

Deploy Server

Other Tools