Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

mailbox_stats

Displays total and unread message counts for every mailbox folder, giving a quick overview of where unread mail is without opening each folder.

Instructions

Show the total and unread message count per folder.

Quick overview ("how many unread where") without opening each folder.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. The verb 'show' implies a read-only, side-effect-free operation, and the 'without opening each folder' phrasing conveys that this is a cheap aggregate rather than per-message retrieval. It does not explicitly confirm read-only behavior, cost, or scoping (e.g. all mailboxes vs. one), which leaves gaps for an unannotated tool, though the risk is low given zero parameters.

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?

Two short lines: the first states what is returned, the second the use case. It is front-loaded, wastes no words, and the parenthetical adds a memorable gloss on the intent.

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?

With zero parameters, a 100%-covered schema, and an output schema that already documents the return shape, the description needs only the purpose and use case, both of which it supplies. An explicit statement that it is read-only across all folders would make it fully complete.

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 no parameters, so there is nothing beyond the schema to explain. The description correctly implies the scope is all folders with no filtering input, which matches the empty argument object. Baseline for zero parameters applies.

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 specific verb and resource: it shows total and unread message counts per folder. An agent can immediately tell this is a lightweight aggregate over folders, which is clearly distinct from message-retrieval tools. It stops short of naming a sibling such as list_mailboxes to sharpen the contrast, so it is clear but not maximally differentiated.

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?

'Quick overview ("how many unread where") without opening each folder' implies when to reach for it, namely as a cheap alternative to opening folders or fetching individual messages. However, it never states explicit alternatives, exclusions, or prerequisites, so the agent must infer the boundary itself.

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