Skip to main content
Glama

get_flash_file_url

Retrieve the download URL for a file in a QQ flash transfer fileset using the fileset ID and optional file index.

Instructions

获取闪传文件链接 fileset_id 来自 create_flash_task、get_fileset_id 或 list_filesets,替换为当前账号可访问的文件集。 file_index 从 0 开始。

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": "get_flash_file_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_nameNo
file_indexNo
fileset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare destructiveHint=false and openWorldHint=true, but they also declare readOnlyHint=false for a tool whose name begins with 'get'. The description does not explain this non-read-only behavior, so it does not tell the agent that the call generates a link or has any side effect. It does add one useful piece of behavioral context: the fileset must be accessible to the current account. It does not mention URL lifetime, permissions, or how the result is returned.

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?

The description is two dense sentences that front-load the purpose and then immediately cover parameter provenance. There is no filler or restatement of the title. The Chinese phrasing is somewhat compressed, especially the clause '替换为当前账号可访问的文件集', which reads as a note appended to the first sentence rather than a clearly separated requirement.

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?

There are three parameters and no output schema, so the description should at least hint at the return value: a URL string, a token, or an object. It says nothing about the return value. Parameter provenance is well covered, but the unspecified file_name parameter and the unexplained readOnlyHint=false setting leave gaps for a tool that performs network access to an external resource.

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

Parameters4/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 the full burden of explaining parameters, and it explains two of the three parameters. It documents fileset_id's provenance and account-scoping, and it notes that file_index is 0-based. The optional file_name parameter is not mentioned at all, so the relationship between file_index and file_name remains ambiguous.

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 gives a specific verb-plus-resource phrase, '获取闪传文件链接', that names both the operation and the resource type (a flash-transfer file). The term '闪传' separates this tool from the sibling tools that return links to group files or private files, such as get_group_file_url and get_private_file_url, but the description never explicitly states that it is not for those. An agent can infer the scope, but the description does not state the exclusion.

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?

The description gives concrete prerequisite guidance: fileset_id comes from create_flash_task, get_fileset_id, or list_filesets, and it must be replaced with a fileset that the current account can access. This is exactly the kind of routing help an agent needs before calling the tool. It stops short of saying when to use this tool instead of the sibling URL tools, and it gives no exclusion rules.

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