Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

check_connection

Verifies the Proton Bridge connection and lists available mailboxes to confirm the mail server is running and credentials are correct.

Instructions

Check the connection to Proton Bridge and list the mailboxes.

For setup diagnostics: verifies that Bridge is running and the
credentials are correct.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description has to carry behavioral disclosure. It does explain the diagnostic purpose (connectivity plus credential validation), but says nothing about failure behavior, whether an error or a structured result reports the failure, or that the call has no side effects — and the mailbox listing is a secondary return behavior that goes undiscussed.

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?

Two short sentences, front-loaded with the primary action and followed by the diagnostic rationale. The second sentence overlaps slightly with "check the connection" but earns its place by naming the two specific checks performed.

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 diagnostic tool with an output schema, this covers enough: what it checks and when to use it. The remaining gap is what a failed check looks like in the response, though the output schema likely covers return shape.

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?

The tool takes zero parameters, so there is no parameter meaning to add beyond the empty schema; baseline 4 applies. The description correctly implies no inputs are needed.

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?

"Check the connection to Proton Bridge and list the mailboxes" gives a concrete verb and resource, so an agent knows exactly what happens. It does not, however, distinguish itself from the sibling list_mailboxes, which also returns mailbox data, leaving ambiguity about which to pick when only mailboxes are wanted.

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?

"For setup diagnostics" supplies a clear usage context, and the second sentence narrows it to verifying that Bridge is running and credentials are correct. There is no explicit when-not guidance and no named alternative such as list_mailboxes for the listing portion.

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