Skip to main content
Glama
Soundhannes

IMAP MCP Server

by Soundhannes

authenticate

Log in to an IMAP email account with username and password to enable email reading, searching, and organization through the IMAP MCP Server.

Instructions

Login with username and password

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesEmail username
passwordYesEmail password or app password
smtpHostNoSMTP server hostname (optional, for drafts)
smtpPortNoSMTP port (default: 587)

Implementation Reference

  • The authenticate method in ImapClientWrapper logs the IMAP client into the server using the provided username and password.
    def authenticate(self, username: str, password: str) -> bool:
        """Login with username and password."""
        if not self.client:
            raise RuntimeError("Not connected. Call connect() first.")
        self.client.login(username, password)
        return True
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Login' implies authentication and potential session creation, it doesn't describe what happens after login (e.g., session persistence, token return, error handling), whether it's idempotent, or any rate limits/security considerations. This leaves significant gaps for a core authentication tool.

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, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a tool with clear parameters and no complex behavioral nuances needing explanation.

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

Completeness2/5

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

For an authentication tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns (e.g., success status, session token, error messages), doesn't address security implications of passing credentials, and doesn't clarify the optional SMTP parameters' purpose. Given the complexity and critical nature of authentication, more context is needed.

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?

Schema description coverage is 100%, so parameters are well-documented in the schema itself. The description adds minimal value beyond implying that username/password are for login, but doesn't clarify why optional SMTP parameters exist or their relationship to authentication versus other operations like 'save_draft'. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Login with username and password' clearly states the action (login) and the required credentials, making the purpose immediately understandable. However, it doesn't differentiate this authentication tool from other connection-related tools like 'connect' or 'auto_connect' in the sibling list, which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'connect' or 'auto_connect' from the sibling list. It also lacks information about prerequisites (e.g., whether this is for initial setup or recurring authentication) or when not to use it (e.g., if already authenticated).

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/Soundhannes/IMAP-MCP'

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