Skip to main content
Glama

maily_download_attachment

Downloads a message attachment to a specified folder or file path, adding a number to the filename if the file already exists to prevent overwriting.

Instructions

Downloads an attachment of a message to disk. dest_path : folder or full path inside ~/Downloads, ~/Desktop or ~/Documents (default: ~/Downloads). An existing file is never overwritten: a number is added to the name.

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": {
      "message_id": "<message_id>",
      "attachment_id": "<attachment_id>"
    },
    "name": "maily_download_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
dest_pathNo
message_idYes
attachment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that writes are confined to ~/Downloads, ~/Desktop, or ~/Documents, that the default is ~/Downloads, and that existing files are never overwritten because a number is appended. It omits what is returned (file path/filename) and what happens on failure, which are the remaining gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no wasted words. The stray line break in the path list is cosmetic rather than substantive.

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

Completeness3/5

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

For a write-to-disk tool with no annotations and no output schema, the description covers the destination constraints and overwrite behavior but leaves the return value, error conditions, and permission requirements unaddressed.

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 coverage is 0%, so the description must compensate. It fully explains dest_path, including the default and the accepted directories, but says nothing about message_id or attachment_id beyond their names.

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 and resource: downloads an attachment of a message to disk. It is clearly distinguishable from the sibling export tool, which saves a whole message, though the description never says so explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the required message_id/attachment_id parameters. It gives no guidance on when to prefer this over maily_export_eml or maily_get_message, and no prerequisites or exclusions.

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