Skip to main content
Glama

radarr_get_download_clients

Read-only

Retrieves configured download clients and their settings from Radarr to verify or troubleshoot movie download client setup.

Instructions

Get download client configurations from Radarr (Movies). Shows configured clients and their settings.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description does not contradict it. The description adds mild context ('shows configured clients and their settings') but says nothing about whether sensitive fields such as credentials or API keys are included or masked in the response — the one behavioral detail that would genuinely matter here.

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?

Two short, front-loaded sentences with no preamble or filler. The second sentence partially restates the first ('Shows configured clients and their settings' vs. 'Get download client configurations'), a small redundancy but not wasteful enough to penalize further.

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

Completeness3/5

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

For a simple read-only, zero-parameter getter this is close to sufficient, but with no output schema the description should sketch the returned shape (client name, protocol, host/port, category, enabled flag) rather than the generic 'their settings'. As written, an agent knows what the tool does but not what it will get back.

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 no parameters, so the baseline is 4; there is no parameter semantics for the description to add or omit. The schema is a bare empty object with full coverage, leaving nothing for prose to compensate for.

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 states a specific verb and resource ('Get download client configurations from Radarr (Movies)') and scopes it to the Movies instance, which distinguishes it from the lidarr_/sonarr_ equivalents. It stops short of naming those siblings explicitly, but the Radarr qualifier makes the target unambiguous.

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 only implied: an agent can infer this is the tool for inspecting configured download clients, but there is no statement of when to prefer it over sibling getters or what task it supports (e.g., auditing client setup before adding a movie). No exclusions or prerequisites are given, which is acceptable for a zero-parameter read.

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