Skip to main content
Glama

Download Alibaba attachment

alibaba_download_attachment

Download an Alibaba conversation attachment by conversation and attachment ID, saving it to a private local cache and returning its local path, name, size, and SHA-256.

Instructions

Save one attachment into the private local cache and return its local path, name, size, and sha256. Requires read or read/write access. Use an id from alibaba_list_attachments. Do not ask for or display the remote address.

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": {
      "conversationId": "<conversationId>",
      "attachmentId": "<attachmentId>"
    },
    "name": "alibaba_download_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
attachmentIdYes
conversationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare it is not read-only and is open-world; the description adds real behavior: content is written into a private local cache rather than returned inline, an access scope is required, and the remote address must not be surfaced. It stops short of disclosing overwrite behavior on repeat downloads or cache-size constraints, which matter given the alibaba_clear_cache sibling.

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?

Three short sentences, front-loaded with purpose and return shape, then requirements, then a security constraint. No filler or restatement of the title.

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

Completeness4/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 usefully names the returned fields, and it covers auth scope and cache locality. The main remaining gap is the unlabeled conversationId and what happens if the same attachment is downloaded twice.

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%, so the description must carry parameter meaning. It explains the provenance of attachmentId (an id from alibaba_list_attachments) but never explains conversationId, its relationship to the attachment, or the required id pattern.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Save one attachment into the private local cache') and enumerates exactly what is returned (local path, name, size, sha256). This clearly separates it from alibaba_list_attachments, which only enumerates ids.

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

Usage Guidelines4/5

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

Gives a concrete prerequisite: the id must come from alibaba_list_attachments, and adds an access-level requirement ('Requires read or read/write access'). It does not state when not to download (e.g., cached copies, size limits), so it is clear context rather than full when/when-not routing.

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