Skip to main content
Glama
Sign In
cfu_mail

cfu_mail

by MrShurukan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

download_attachment

Downloads an email attachment from a specified IMAP account, folder, and message part to a generated local path without executing the file.

Instructions

Download an attachment to a generated local path. Never execute the file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_id": "<account_id>",
      "folder": "<folder>",
      "uidvalidity": "<uidvalidity>",
      "uid": "<uid>",
      "part_id": "<part_id>"
    },
    "name": "download_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
folderYes
part_idYes
account_idYes
uidvalidityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description usefully explains WHY it is not read-only (it writes to a generated local path the caller does not supply) and adds a security constraint about not executing the downloaded file. It stops short of stating where the path appears or how errors surface.

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?

Two sentences, no filler, with the action and destination stated first and the security caution second. Every clause carries weight.

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 a tool with five required, undocumented parameters, no output schema, and a filesystem side effect, the description omits the parameter meanings and whether the generated path is returned to the caller. Without an output schema the description should say something about the return value, and it does not.

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

Parameters2/5

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

Schema coverage is 0% across five required parameters, including opaque IMAP terms like uidvalidity and part_id, and the description explains none of them. Only the notion of a "generated local path" hints at behavior (the caller does not choose a destination), which is minimal compensation for a total documentation gap.

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?

States a specific verb (download) and resource (attachment) plus where the file lands (a generated local path), so the agent knows the action precisely. It does not differentiate from siblings, though none of the listed siblings are competing download tools.

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 only guidance is a safety warning ("Never execute the file"), which is about handling the result, not about when to pick this tool. There is no statement of preconditions (e.g., must have retrieved message metadata first) and no reference to alternatives such as preview_draft or read_message.

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

Deploy Server

Other Tools