Skip to main content
Glama

amulen_download_attachment

Download a task attachment to a local folder and return its saved path for opening or analysis; existing files are never overwritten.

Instructions

Download a task attachment to a local folder (default: ~/Downloads/amulen/<task_slug>/). Returns the saved path so you can open or analyze the file. Never overwrites existing files.

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": {
      "project_slug": "<project_slug>",
      "board_slug": "<board_slug>",
      "task_slug": "<task_slug>",
      "attachment_id": "<attachment_id>"
    },
    "name": "amulen_download_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
destinoNo
task_slugYes
board_slugYes
project_slugYes
attachment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, openWorldHint=true and destructiveHint=false; the description usefully confirms the non-destructive promise with 'Never overwrites existing files' and discloses the default local path and that the saved path is returned. It does not explain what happens on a name collision (a new file, an error, or a suffix), nor whether the destination directory must already exist, so the overwrite behavior is only half-specified.

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?

Three compact sentences, front-loaded with the core action and destination, followed by the return value and the non-destructive guarantee. Every sentence carries information; no filler or repetition of the tool name.

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?

With no output schema, the description helpfully states that the saved path is returned, and it covers the default destination. But for a 5-parameter tool with 0% schema coverage, missing guidance on sourcing attachment_id and the meaning of the three slug parameters leaves a real gap for an agent trying to construct a valid call.

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 0% across 5 parameters, so the description bears the full burden. It does explain the destino parameter's default and the path template that embeds task_slug, which is genuine added meaning, but project_slug, board_slug and attachment_id are left entirely uncharacterized (how to obtain the id, format expectations).

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 opens with a specific verb plus resource: 'Download a task attachment', and adds the destination scope (local folder with a default path). It is immediately distinguishable from amulen_upload_attachment and amulen_list_attachments by action alone. It stops short of explicitly naming a sibling it complements, which keeps it from a 5.

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: the agent infers this is the tool to call once it has an attachment, but the description never says to call amulen_list_attachments first to obtain the required attachment_id, nor states any precondition. No when-not guidance or alternatives are offered.

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