Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

ai_digest

Generates a prioritized, read-only AI overview of a mailbox, showing one line per message by importance and flagging which messages need a reply.

Instructions

Prioritized AI overview of the mailbox (read-only): sorted by importance, one line per message, marks what needs a reply.

Needs ANTHROPIC_API_KEY. Free alternative without a key: digest_bundle.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
folderNoINBOX

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well by stating that the operation is read-only, that results are sorted by importance, and that it requires ANTHROPIC_API_KEY. It does not explain failure behavior without a key or how folder and limit affect results.

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?

The description is two sentences, front-loads the core function, and uses the remainder for the key requirement and free alternative. There is no filler.

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?

An output schema exists, so return formatting need not be explained, and the key requirement plus alternative are covered. However, for a two-parameter tool with no schema parameter descriptions, the missing limit and folder semantics leave a clear gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero-percent description coverage for limit and folder, and the description does not explain either parameter. It only refers generally to a mailbox overview, leaving the effect of folder selection and result limiting undocumented.

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 verb-like function and resource: a prioritized AI overview of the mailbox, sorted by importance, one line per message, and marking replies needed. It also distinguishes itself from the free sibling digest_bundle by requiring an API key.

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?

It clearly says to use digest_bundle instead when no ANTHROPIC_API_KEY is available, which is a useful alternative condition. It does not clarify when to choose this over AI analysis or triage siblings, but the key-based routing is explicit.

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