Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

folder_stats

Get live message count, unseen count, uidNext, and uidValidity for a specific mailbox folder to check unread counts or folder health without fetching messages.

Instructions

Return live message count, unseen count, uidNext, and uidValidity for a single mailbox folder. Use to check unread counts or folder health without fetching messages. Prefer count_messages when you need to apply filters (sender, subject, date). Prefer get_email_stats for an aggregate summary across all folders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNoFolder path. Defaults to INBOX.INBOX

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.37
    • removedInput schema / properties / scanLimit
      Removed value: -{
-  "description": "Maximum messages to scan (1–20000, default 5000). Lower = faster but less accurate.",
-  "type": "number"
-}
  2. Addedv1.17.0
  3. Removedv1.13.11
  4. Changed1 schema field changedv1.13.11
    • addedInput schema / properties / folder / default
      Added value: +"INBOX"
  5. Addedv1.13.4

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It says 'live' and 'without fetching messages', implying read-only, but does not explicitly state it is read-only or side-effect-free. It also doesn't mention error conditions or rate limits, but for a simple stats tool the behavior is largely implied.

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 with zero wasted words. The first sentence states the exact return values and scope, and the second provides usage guidance with named alternatives. It is front-loaded and highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one optional parameter and no output schema, the description is complete. It explains what it returns, when to use it, and how it differs from siblings. Nothing an agent needs to call it correctly is missing.

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?

The schema has 100% description coverage for the single parameter 'folder', with a clear description. The tool description adds 'single mailbox folder' context but does not add any new syntax or format details beyond what the schema already provides, so the baseline of 3 is appropriate.

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 clearly states the tool returns live message count, unseen count, uidNext, and uidValidity for a single mailbox folder. It explicitly distinguishes itself from siblings by naming count_messages (for filters) and get_email_stats (for aggregate summaries), making it unambiguous which tool is which.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool (check unread counts or folder health without fetching messages) and when to prefer alternatives (count_messages for filters, get_email_stats for aggregate across folders). This is exactly the kind of routing guidance an agent needs.

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

Deploy Server

Other Tools