Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

search_indexed_emails

Read-only

Search your locally indexed Proton Mail offline using free-text or field shortcuts (from, to, subject, label). Use when the index is up-to-date for fast results without IMAP connection.

Instructions

Search the local SQLite mailbox index without making any IMAP connection. Supports free-text and field shortcuts inline: from:alice@example.com, to:bob, subject:invoice, label:Archive, domain:acme.com. Use for fast, offline-capable searches when the index is populated. Prefer search_emails when you need live IMAP results or when the index is stale or empty. Prefer this over search_emails when the index is current. Use search_emails if messages were received after the last sync.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text query across indexed metadata.
folderNoFolder filter.
labelNoFolder or label filter.
threadIdNoThread id filter.
fromNoSender filter.
toNoRecipient filter.
senderDomainNoSender domain filter such as example.com.
subjectNoSubject filter.
hasAttachmentNoAttachment filter.
attachmentNameNoAttachment filename filter.
isReadNoRead status filter.
isStarredNoStarred status filter.
mailboxRoleNoNormalized mailbox role like Inbox, Sent, Archive, or Trash.
dateFromNoInclusive start date/time in ISO format.
dateToNoInclusive end date/time in ISO format.
limitNoMaximum results.
Behavior4/5

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

The description adds value beyond annotations by explaining the tool makes no IMAP connection and works offline. Annotations already declare readOnlyHint=true, so no contradiction.

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 concise (4 sentences), front-loaded with the core purpose, and every sentence adds essential information without redundancy.

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?

Given no output schema, it covers purpose, offline behavior, usage conditions, and inline shortcuts. Missing details on empty index behavior, but overall sufficient for a search tool.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining inline field shortcuts (e.g., from:, subject:) that are not in the schema, enhancing usability.

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 it searches a local SQLite mailbox index without IMAP, and explicitly distinguishes itself from the sibling tool search_emails by noting offline capability.

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?

Provides explicit guidance on when to use this tool (index current, offline) vs. search_emails (live IMAP, stale index), including a specific condition about messages received after last sync.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googlarz/proton-mail-bridge-client'

If you have feedback or need assistance with the MCP directory API, please join our Discord server