Skip to main content
Glama
synology-mcp
by r03eRt

Download Station: task details

downloads_get
Read-only

Retrieve complete details for specified Synology Download Station tasks, including source URL, owner, peers, torrent files, and trackers. Use task IDs from the download list to inspect individual downloads.

Instructions

Full details of download tasks: source URL, owner, peers, files inside a torrent and trackers.

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": {
      "ids": "<ids>"
    },
    "name": "downloads_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesTask ids as returned by downloads_list, e.g. ["dbid_1166"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, closed-world operation. The description adds useful context about the returned fields, but it does not describe response structure, error behavior for missing ids, or other operational details, and there is no output schema to compensate.

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 front-loaded sentence that lists the key returned fields without filler. Every phrase contributes to explaining what the tool provides.

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 simple read-only getter with one well-documented parameter and annotations covering safety, the description provides a useful summary of returned data. It is nearly complete, though additional usage or error-context guidance would strengthen it.

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 input schema has 100% description coverage for the single ids parameter, including an example format. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline score of 3 applies.

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?

The description clearly identifies the resource as download tasks and states that it returns full details, listing specific fields such as source URL, owner, peers, torrent files, and trackers. It distinguishes itself from a simple list operation through the emphasis on full details, though it does not explicitly name or contrast with siblings like downloads_list or downloads_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not state when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. Usage is only implied by the purpose of retrieving full task details.

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