Skip to main content
Glama
Sign In
FluxDown

FluxDown

by zerx-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

download_list

List download tasks filtered by status (all, pending, downloading, paused, completed, error, preparing). Returns each task's progress, speed, and state.

Instructions

列出下载任务，可按状态过滤。返回任务数组（含进度、速度、状态等）。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "download_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo按状态过滤（省略或 all = 全部）。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Description specifies that it returns an array with progress, speed, and status, clarifying the read-only nature. No annotations provided, so description carries burden. Could improve by stating no side effects.

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?

Two concise sentences with no superfluous text. Front-loaded with verb and resource.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one optional parameter and no output schema, the description adequately covers purpose, filtering, and return structure.

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?

Parameter semantics are fully covered by schema (100% coverage). Description adds minimal value by listing return fields but does not elaborate beyond schema.

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?

Description clearly states '列出下载任务' (list download tasks) and mentions filtering by status, distinguishing it from sibling tools like download_add or download_get.

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?

Description implies usage for listing tasks with optional status filter, but does not explicitly state when to use this tool instead of alternatives like download_get or queue_list.

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