mailpouch

Overview Schema Source Related Servers Discussions Admin

Setup & Connection Status

setup_status

Read-only

Diagnose a mailpouch email setup and get the single next action to resolve missing credentials, unreachable Proton Bridge, or unapproved agent access. Works before credentials or approval.

Instructions

CALL THIS FIRST. Diagnoses the mailpouch install end-to-end and returns the single next action to get connected: whether credentials are configured, whether Proton Bridge is reachable, and whether this agent's access has been approved. Always available — works even before the agent is approved or credentials are set. Use get_connection_status afterwards for live IMAP/SMTP auth health.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`account_id`	No	Optional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).

Output Schema

TableJSON Schema

Name	Required	Description
`imap`	No
`smtp`	No
`state`	Yes	Overall install state — pick the next step from this.
`nextStep`	Yes	The single most-important action to take next.
`username`	No
`configPath`	No	Path to the config file (default ~/.mailpouch.json; overridable via the MAILPOUCH_CONFIG env var). Redacted to '~/.mailpouch.json' for callers whose grant is not yet active.
`configured`	Yes	A username and Bridge password are configured.
`grantStatus`	No	This agent's per-agent grant state, or null when the local-agent gate is off.
`insecureTls`	No	TLS validation is disabled (no pinned Bridge cert).
`configExists`	No
`bridgeReachable`	Yes	Both IMAP and SMTP Bridge ports accept TCP connections.
`credentialStorage`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.1.0Jul 5, 2026

addedInput schema / properties / account_id

Added value: +{
+  "description": "Optional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).",
+  "type": "string"
+}

First observedv3.0.77Jun 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is clear. The description adds behavioral details like 'returns the single next action' and 'always available', which go beyond annotations and help the agent understand what happens.

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?

Description is three sentences, front-loaded with the imperative 'CALL THIS FIRST', and no redundant information. Every sentence adds value.

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?

Given the tool has an output schema (not shown but referenced), the description adequately explains what it returns (single next action) and when it's available. It covers all necessary context for a diagnostic tool.

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 covers the single optional parameter (account_id) with a clear description (100% coverage). The main description does not add new parameter details, which is acceptable given the schema quality, earning a baseline score.

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 explicitly states 'CALL THIS FIRST' and clarifies it diagnoses end-to-end connectivity, listing specific checks (credentials, Proton Bridge reachability, agent access). It distinguishes itself from the sibling 'get_connection_status' by specifying the latter is for live IMAP/SMTP health.

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?

The description provides clear usage context: 'CALL THIS FIRST' and 'Use get_connection_status afterwards'. It also notes it works even before the agent is approved or credentials are set, setting expectations for when to invoke.

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

Deploy Server