Skip to main content
Glama
Sign In
FluxDown

FluxDown

by zerx-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

download_remove

Delete a download task by ID, with an option to also remove downloaded files from disk.

Instructions

删除指定任务，可选同时删除已下载的磁盘文件。

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": {
      "taskId": "<taskId>"
    },
    "name": "download_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes任务 ID（必填）。
deleteFilesNo是否同时删除磁盘文件（默认 false）。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The description discloses the core behavior (deletion) and an optional destructive action (file deletion). Without annotations, it adequately conveys the main side effect but does not mention irreversibility, prerequisites, or potential impact on other tasks.

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?

The description is a single, concise sentence that front-loads the primary action and nests the optional behavior efficiently. Every word serves purpose without redundancy.

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?

For a deletion tool with no output schema, the description covers the essential action and optional file removal. It does not mention return values or prerequisites, but these are not critical for a straightforward operation. Sibling tools provide cluster context.

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 coverage is 100%, so the description's paraphrase of taskId and deleteFiles adds minimal new information. The description explains deleteFiles as 'optional delete downloaded disk files', which mirrors the schema description, thus providing no added semantic depth.

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?

The description clearly specifies the verb '删除' (delete) and the resource '指定任务' (specified task), effectively distinguishing it from sibling tools which focus on adding, getting, listing, pausing, or resuming tasks.

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 implies usage for task removal and optionally file deletion, providing clear context. However, it lacks explicit guidance on when to choose this tool over alternatives or any exclusions (e.g., cannot remove active tasks).

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