Skip to main content
Glama

List download tasks

nas_download_list
Read-only

List NAS download center tasks with progress percentages, either all tasks or specific task IDs. Check status until COMPLETED, FAILED or PAUSED to monitor downloads.

Instructions

Show the tasks of the NAS download center with their progress. Without task_ids it lists every task, including finished ones; with task_ids it returns just those, and fails as a whole if any ID does not exist. Tasks are in data.tasks[]. Use progress_percent (a number from 0 to 100) rather than dividing bytes: total_bytes can be negative while the size is unknown. saved_path and file_name are empty until task_status is TASK_STATUS_COMPLETED, which does not mean failure. When waiting for a task, check a few seconds apart and stop at COMPLETED, FAILED or PAUSED; the access token has a per-minute request quota.

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

Input Schema

NameRequiredDescriptionDefault
task_idsNoTask IDs to query; omit to list all tasks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations it discloses several non-obvious behaviors: the whole call fails if any requested ID does not exist, total_bytes can be negative while size is unknown, saved_path and file_name stay empty until TASK_STATUS_COMPLETED (which is not a failure state), and there is a per-minute access-token quota. These are exactly the operational facts annotations cannot convey.

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?

Front-loaded with the tool's purpose and the mode split, then progressive detail on return shape, values to trust, and polling. Every sentence carries distinct information with no restatement of the name or annotations.

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?

There is no output schema, so the description compensates by naming the result path (data.tasks[]), the field to use for progress, the sentinel meaning of TASK_STATUS_COMPLETED, and the terminal states for polling. Nothing an agent needs in order to call this correctly is missing.

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 100% for the single task_ids parameter, so the baseline is 3, but the description adds real meaning: the omit-vs-supply semantics of the whole list, and the all-or-nothing failure when one ID is invalid. The 50-item cap and per-item minLength remain schema-only, which is fine.

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?

States a specific verb and resource ('Show the tasks of the NAS download center with their progress') and immediately disambiguates the two modes: list everything when task_ids is omitted, return only the named tasks otherwise. That is enough for an agent to distinguish it from the file, docker, and status siblings without opening the schema.

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?

Gives explicit conditional guidance (omit task_ids to list all, supply them to query specific tasks) and concrete polling advice with stop conditions: check a few seconds apart and stop at COMPLETED, FAILED or PAUSED. No alternative tool is named, so it falls short of the 5 mark, but the when-to-use context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.