proton-mcp

Overview Schema Source Related Servers Discussions Admin

Work on mail filters

manage_filters

Read-only

Explains how to manage Proton Mail filters manually, including reading, proposing, applying, reordering, deleting, and toggling rules, and guides users when the helper extension is inactive.

Instructions

Explains how to work on Proton Mail filters, the rules for sorting incoming mail, by hand: through Proton's settings page in a browser, in Sieve, with the user agreeing to each change. Reading, proposing, applying, moving, deleting and switching filters goes through list_filters, get_filters, propose_filter, apply_filter, reorder_filters, delete_filter and set_filter_status, which use the browser extension Proton MCP Helper; call this when they report that the extension is not active, or when the user wants to make a change themselves.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "manage_filters"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.13Nov 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already mark it read-only and closed-world; the description adds useful context that it explains a manual browser/Sieve process and requires user agreement for each change. It does not describe the form of the guidance returned, so it falls short of a 5.

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?

The purpose is front-loaded, and the sibling-tool list is relevant for routing. The second sentence is dense and could be split, but no sentence is pure filler.

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 zero-parameter informational tool with read-only annotations and no output schema, the description covers when to use it and what alternatives exist. It could say more about what the guidance response contains, but the core routing context is present.

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 are no input parameters, and schema coverage is 100%; the baseline for a zero-parameter tool is 4. The description has no parameters to clarify, so no additional semantic detail is needed.

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 a specific action, 'Explains how to work on Proton Mail filters ... by hand,' and identifies the resource clearly. The second sentence distinguishes it from the sibling filter-operation tools, making clear this is a manual/fallback guidance tool rather than a filter mutator.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit call conditions: when the extension is not active or when the user wants to make changes themselves. It also names the alternative tools for reading, proposing, applying, moving, deleting, and switching filters, so the when/when-not routing is complete.

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