Skip to main content
Glama
chandshy
by chandshy

Setup & Connection Status

setup_status
Read-only

Diagnoses the mailpouch install end-to-end and returns the single next action to connect: checks credentials, Proton Bridge reachability, and agent approval. Works before setup is complete.

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
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYesOverall install state — pick the next step from this.
configuredYesA username and Bridge password are configured.
bridgeReachableYesBoth IMAP and SMTP Bridge ports accept TCP connections.
configExistsNo
configPathNoPath 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.
usernameNo
credentialStorageNo
imapNo
smtpNo
insecureTlsNoTLS validation is disabled (no pinned Bridge cert).
grantStatusNoThis agent's per-agent grant state, or null when the local-agent gate is off.
nextStepYesThe single most-important action to take next.
Behavior5/5

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

The description adds context beyond the readOnlyHint annotation by explaining that the tool is always available, even before the agent is approved or credentials are set, indicating its non-destructive, diagnostic nature. No contradictions with annotations.

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 a single, well-structured paragraph. It starts with the critical instruction 'CALL THIS FIRST', then concisely explains the tool's functionality and follow-up. Every sentence adds value with no unnecessary words.

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 zero parameters, good annotations, and the presence of an output schema, the description is complete. It explains the tool's purpose, usage, availability, and output, leaving no gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the schema is already fully covered. The description doesn't need to add parameter info, and it focuses on the tool's behavior and output.

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's purpose: diagnosing a mailpouch install end-to-end and returning the single next action to get connected. It specifies what it checks (credentials, Proton Bridge reachability, agent approval) and distinguishes it from sibling tool 'get_connection_status'.

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 explicitly says 'CALL THIS FIRST' and advises using 'get_connection_status afterwards for live IMAP/SMTP auth health', providing clear when-to-use and when-not-to-use guidance with a named alternative.

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/chandshy/mailpouch'

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