Skip to main content
Glama
synology-mcp
by r03eRt

Download Station: list downloads

downloads_list
Read-only

List Synology download tasks with status, progress, size, speed, and destination; filter by status, type, or title text and get counts per status.

Instructions

List download tasks with status, progress, size, speeds and destination. Filter by status, type or text in the title. Also returns how many tasks there are in each status.

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

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNoMax tasks to return (default 50)
queryNoCase-insensitive text to look for in the title
offsetNo
statusNoOnly tasks in these statuses, e.g. ["downloading","error"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the non-obvious fact that the result includes per-task telemetry and an aggregate count per status, which is genuine value beyond the annotation. It does not mention the default page size (limit=50) or ordering, leaving pagination behavior undisclosed.

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?

Three short sentences, front-loaded with the core action and return contents, followed by filtering and the aggregate count. No filler, though the returned-fields list and the filter list could be tightened into one sentence without loss.

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 read-only listing tool with no output schema, the description generously explains what comes back, including the per-status totals. The main gap is pagination: how results are paged, the default of 50, and how to retrieve further pages is not addressed anywhere in the description.

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?

The description restates three of five parameters (status, type, query) in plain language but adds little beyond the schema's own descriptions, and it is silent on the two pagination parameters limit and offset. With 60% schema coverage, the schema carries most of the weight, so the baseline 3 is appropriate.

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?

States a specific verb and resource ("List download tasks") and enumerates the fields returned (status, progress, size, speeds, destination), so an agent knows exactly what it gets back. It never names the near-siblings downloads_get or downloads_info, so the boundary between listing and fetching a single task must be inferred from the names alone.

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?

Usage is implied by the filtering sentence: use this when you want a status/type/title-filtered view of the task queue. There is no explicit when-not or pointer to downloads_get/downloads_info when a single task's detail is wanted, so the agent must choose between siblings unaided.

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