Skip to main content
Glama

download_fileset

Resolves a direct download URL for a QQ flash transfer fileset by fileset_id, returning the URL, file name, and size so the caller can handle the actual download.

Instructions

解析闪传文件下载直链(不下载,由调用方实现下载) fileset_id 来自 create_flash_task、get_fileset_id 或 list_filesets,替换为当前账号可访问的文件集。 file_index 从 0 开始。 Returns: { url, file_name, file_size }

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": {
      "fileset_id": "<fileset_id>"
    },
    "name": "download_fileset"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_nameNo
file_indexNo
fileset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description usefully adds that no file transfer occurs and that the caller performs the download, which resolves the misleading 'download' verb. It does not, however, cover URL lifetime/expiry, permission requirements beyond '当前账号可访问', or why a non-read-only operation is needed to resolve a link.

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?

Front-loaded with the key caveat (resolve, don't download) followed by parameter notes and a return shape, with no filler. The mixed Chinese/English phrasing is slightly uneven but every clause carries information.

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 correctly supplies the return shape { url, file_name, file_size }, and it explains the two non-obvious parameters. The only meaningful omission is the purpose of the optional file_name parameter, which an agent might otherwise misuse.

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 compensate: it explains fileset_id's origin and that file_index is 0-based, which is genuine added meaning. The third parameter, file_name, is never mentioned, leaving a gap that neither the schema nor the description fills.

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 states a specific verb and resource ('解析闪传文件下载直链' – resolve a flash-transfer file's direct download URL) and immediately disambiguates it from the many download_file* siblings by noting it does not perform the download itself. An agent can distinguish it from the sibling tools without opening a schema, though it never names a specific alternative.

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?

It gives concrete provenance guidance for fileset_id ('来自 create_flash_task、get_fileset_id 或 list_filesets'), which tells the agent how to obtain the required input and routes it to the right upstream tools. The '不下载,由调用方实现下载' clause clarifies the division of labour, but no explicit when-not-to-use condition is stated.

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