Loading ToolBench
Agente Proton Suite con MCP server embebido: Mail (Bridge IMAP/SMTP), Pass (pass-cli), Drive — 47 tools por defecto (50 con Calendar experimental), auto-configuración, organización inteligente y alertas de seguridad.
31 tools with mixed quality. Naming is consistent (verb_noun pattern: proton_list_*, proton_send_*, proton_delete_*) and follows conventions well. Descriptions are present but brief (avg ~60 chars, well below the 194-char baseline for A+ tools). Input schemas visible for most write/destructive tools but many lack depth, parameters have types and descriptions, but lack constraints (enums, ranges, patterns). Output schemas are not documented. Error handling guidance is absent. Security-sensitive tools (proton_bridge_login, proton_pass_insert) accept credentials as parameters, violating secret-injection pattern. Calendar tools are marked experimental stubs with minimal implementation. Read-only tools (proton_list_folders, proton_suite_status) have no input schema documented.
Plan agent actions for email organization and security
Authenticate with Proton Mail Bridge
Logout from Proton Mail Bridge
Create a calendar event (experimental stub)
List calendars (experimental stub)
Create a new IMAP folder
Delete a message (move to Trash)
Credentials exposed as tool parameters: proton_bridge_login accepts username and password as parameters. Secrets in parameters are logged in traces and prompt history, violating secret-injection pattern. Move to server-side environment variable or vault injection.
Output schemas not documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., what fields does proton_list_messages return? Does it include message_id for proton_get_message?). Add explicit return type documentation.
No input constraints on parameters. folder, path, email, and other string parameters lack enums, regex patterns, or length limits. LLMs will hallucinate invalid values. Add constraints: folder must be one of [Inbox, Sent, Drafts, ...]; email must match RFC 5322; path must not contain '..'.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2025-06-18+ | v2 |
Audit Proton Drive for security issues and organization
Copy a file or folder in Proton Drive
Create a new folder in Proton Drive
Download a file from Proton Drive
Move a file or folder in Proton Drive
Organize files in Proton Drive based on rules
Delete a file or folder from Proton Drive
Share a file or folder in Proton Drive
Upload a file to Proton Drive
Install or update Proton ecosystem tools
Set or clear flags on a message (starred, read, etc.)
Forward a message to another recipient
Fetch full message body and metadata by UID
List IMAP folders with message counts and flags
List messages in a folder with pagination and filtering
Move a message to another folder
Copy a password entry within Pass store
Generate a new password and store it
Insert a new password entry into Pass store
Move a password entry within Pass store
Remove a password entry from Pass store
Reply to a message
Send an email via SMTP
Get status of all Proton Suite products
Descriptions are too brief (avg 50 chars vs 194-char baseline). Many lack context on WHEN to use the tool or what it returns. E.g., 'Audit Proton Drive for security issues and organization' does not explain what issues are detected or how results are structured. Expand to 100-200 chars with actionable guidance.
No error handling guidance. Tools do not document what errors can occur, whether they are retryable, or what the LLM should do next. E.g., proton_send_email may fail if recipient is invalid, but no guidance on recovery. Add error classification and recovery hints.