Skip to main content
Glama
synology-mcp
by r03eRt

Download Station: status and settings

downloads_info
Read-only

Retrieves Download Station status details, including version, management status, default destination folder, speed limits, and current total download/upload speeds.

Instructions

Download Station version, whether the user manages it, default destination folder, speed limits and the current total download/upload speed.

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that it bundles static settings together with live aggregate transfer speeds, which is useful context, but it does not mention freshness, whether values are per-user or instance-wide, or the response shape.

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?

A single compact clause with no filler, and the most identifiable item (Download Station version) is front-loaded. It reads as a field list rather than a sentence, which is acceptable but slightly less scannable than a verb-first opener.

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 zero-parameter read-only tool with no output schema, the description usefully enumerates the returned fields, which substitutes for missing return documentation. Given the low complexity, only the absence of usage routing keeps it from being fully complete.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics to add or omit.

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 enumerates the specific resource contents (Download Station version, managed-by-user flag, default destination folder, speed limits, current aggregate up/down speed), so an agent can tell what data it yields. It lacks an explicit verb ('get/retrieve') and never contrasts itself with look-alike siblings such as get_info or get_system_info, so it is clear but not fully differentiated.

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?

There is no when-to-use or when-not-to-use statement and no pointer to an alternative among the many get_*/downloads_* siblings. An agent must infer that this is the configuration/status read rather than a task listing.

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