Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

check_email_auth

Checks email authentication with SPF, DKIM, and DMARC, plus From vs. Return-Path and display-name spoofing, returning per-message auth status, risk score, and warning signs for quick triage.

Instructions

Deterministic phishing/spoofing check (SPF/DKIM/DMARC, From vs. Return-Path, display-name spoofing) - NO AI, no API key, no cost.

uids = a single uid OR a list. Returns the auth status, a heuristic risk (0-100) and warning signs per message - enough for the MCP client's own model to triage.

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": {
      "uids": "<uids>"
    },
    "name": "check_email_auth"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidsYes
folderNoINBOX

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/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 reasonably well: it discloses determinism, absence of external dependencies/cost, and that output includes auth status, a 0-100 heuristic risk, and per-message warning signs. It does not state whether the operation is read-only or whether it performs live DNS lookups that could be slow or fail.

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?

Front-loaded with the capability and its differentiators, then the parameter and return summary. Compact with no filler, though the mid-sentence line break is slightly awkward.

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 spelled out, and the description still summarizes them usefully. The main gap is the unmentioned folder parameter and the lack of any statement about read-only behavior or network dependencies.

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. It usefully resolves the anyOf ambiguity by stating 'uids = a single uid OR a list', but the folder parameter (default INBOX) is never mentioned, leaving one of two parameters 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?

Names a specific verb and resource ('phishing/spoofing check') and enumerates the concrete signals it evaluates (SPF/DKIM/DMARC, From vs. Return-Path, display-name spoofing). The 'NO AI' framing also separates it from the ai_analyze_email sibling without needing that name.

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?

The 'NO AI, no API key, no cost' line and the closing note that results are 'enough for the MCP client's own model to triage' imply this is the cheap deterministic alternative to AI-based analysis, but no explicit when-to-use or when-not-to-use statement is given.

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