Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

surface_priority

Prioritizes mail from protected senders by placing matching messages at the top of your mailbox view using client-side decoded From and Subject matching, including non-ASCII terms. Read-only.

Instructions

Pull mail from protected senders to the TOP - the offensive counterpart of the protected list. Uses the entries of protected_senders.txt and matches them client-side against the decoded From and Subject, so non-ASCII terms work too. Read-only, moves nothing.

only_unseen=False scans the newest candidates (up to 500); extra_terms
(comma-separated string or list) adds more terms, e.g. specific names.

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": "surface_priority"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
folderNoINBOX
extra_termsNo
only_unseenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full load and does well: it declares read-only behavior ('moves nothing'), discloses the client-side matching strategy against decoded From and Subject, and notes non-ASCII support. It also explains the scan bound (up to 500 candidates when only_unseen=False), though it omits what happens if protected_senders.txt is missing or how results are ordered.

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 in the first sentence, followed by behavioral detail and then parameter notes, with no filler sentences. The line-broken formatting is slightly awkward but the content density is high and every clause carries information.

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?

An output schema exists, so return values need not be described, and the description adequately covers the tool's unusual mechanics (client-side matching, priority surfacing, read-only). The main remaining gaps are the undocumented limit and folder parameters and the absence of guidance on failure when the protected list is empty.

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 coverage is 0%, so the description must compensate for four parameters, and it only covers two: only_unseen (explaining that False scans up to 500 newest candidates) and extra_terms (with format options and an example). limit and folder are left entirely to the schema, which supplies only titles and defaults, so the description is helpful but materially incomplete.

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 states a concrete verb and resource: 'Pull mail from protected senders to the TOP', and clarifies it is the counterpart of the protected list. It distinguishes itself from generic retrieval by naming the protected_senders.txt source, though 'to the TOP' leaves some ambiguity about whether it reorders the mailbox or just ranks returned results (partially resolved by 'moves nothing').

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

Usage Guidelines3/5

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

Usage is implied through the 'offensive counterpart of the protected list' framing and the note about extra terms, giving an agent a sense of when priority surfacing is appropriate. However, it never names a sibling alternative (e.g. search_emails) or states when NOT to use this tool, leaving routing decisions partly to inference.

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