Skip to main content
Glama

delete_flash_file

Destructive

Deletes a flash file by fileset_id to remove a file set from the current QQ account. Use the ID from create_flash_task, get_fileset_id, or list_filesets.

Instructions

删除闪传文件 fileset_id 来自 create_flash_task、get_fileset_id 或 list_filesets,替换为当前账号可访问的文件集。

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

Input Schema

NameRequiredDescriptionDefault
fileset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds only a mild ownership constraint and leaves critical behavior unstated: whether the whole fileset or one file inside it is removed, whether deletion is permanent, and what happens to shared recipients.

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?

One compact sentence, front-loaded with the verb and resource, then the parameter provenance. No filler, though the provenance list lengthens it slightly and the ownership clause is a bit awkwardly appended.

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 destructive single-parameter tool with full annotation coverage and no output schema, the definition covers how to obtain the id but not the scope of what is destroyed. An agent could invoke it correctly, yet without knowing if the whole fileset disappears.

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 coverage is 0% and the single parameter has no inline documentation, so the description carries the burden. It does so well by naming the three sibling tools that produce a valid fileset_id and by noting that the id must refer to a fileset accessible to the current account.

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?

"删除闪传文件" names a specific verb and a specific resource (flash-transfer files), which separates it from generic deletion siblings such as delete_group_file or delete_msg. It stops short of an explicit contrast with those siblings, but the resource itself is unambiguous.

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?

The description usefully explains where fileset_id must come from (create_flash_task, get_fileset_id, list_filesets) and constrains it to filesets the current account can access. It gives no when-not-to-use guidance, no warning about consequences of deletion, and no alternative for removing a single file versus an entire fileset.

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