Skip to main content
Glama
Soundhannes

IMAP MCP Server

by Soundhannes

get_attachments

Retrieve and list file attachments from a specific email in an IMAP mailbox using its unique identifier.

Instructions

List attachments of an email

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesEmail UID
mailboxNoMailbox name (default: current)

Implementation Reference

  • The implementation of the get_attachments tool in the ImapClientWrapper class.
    def get_attachments(self, uid: int, mailbox: Optional[str] = None) -> list[Attachment]:
        """List attachments of an email."""
        self._ensure_connected()
        if mailbox:
            self.select_mailbox(mailbox)
    
        data = self.client.fetch([uid], ["BODY[]"])
        if uid not in data:
            raise ValueError(f"Email with UID {uid} not found")
    
        raw_body = data[uid].get(b"BODY[]", b"")
        msg = email.message_from_bytes(raw_body)
        return self._extract_attachment_info(msg)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('List attachments') but does not describe what the output includes (e.g., file names, sizes, types), whether it requires authentication, or if there are rate limits. This is a significant gap for a tool with no structured behavioral hints.

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 with no wasted words. It is front-loaded with the core action, making it easy to grasp quickly. Every part of the sentence contributes directly to stating the tool's purpose.

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?

Given the complexity of listing attachments (which could involve multiple data points) and the lack of annotations and output schema, the description is incomplete. It does not explain what information is returned (e.g., attachment metadata), leaving the agent uncertain about the tool's full behavior and output.

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 the input schema already documents the parameters ('uid' and 'mailbox') fully. The description does not add any meaning beyond this, such as explaining what an email UID is or how mailbox names are formatted. Baseline 3 is appropriate as the schema handles 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 'List attachments of an email' clearly states the verb ('List') and resource ('attachments of an email'), making the purpose understandable. However, it does not distinguish this tool from sibling tools like 'download_attachment' or 'get_email', which might also involve attachments or email data, so it lacks explicit differentiation.

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. For example, it does not specify if this should be used before downloading attachments or as part of email retrieval, nor does it mention prerequisites like needing an email UID. This leaves usage context unclear.

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