Skip to main content
Glama

radarr_get_download_clients

Retrieve configured download client settings from Radarr to manage movie downloads and monitor connection status.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for 'radarr_get_download_clients': parses tool name to get service, retrieves RadarrClient instance, calls getDownloadClients(), formats response as summarized JSON with client details.
    case "sonarr_get_download_clients":
    case "radarr_get_download_clients":
    case "lidarr_get_download_clients":
    case "readarr_get_download_clients": {
      const serviceName = name.split('_')[0] as keyof typeof clients;
      const client = clients[serviceName];
      if (!client) throw new Error(`${serviceName} not configured`);
      const downloadClients = await client.getDownloadClients();
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: downloadClients.length,
            clients: downloadClients.map(c => ({
              id: c.id,
              name: c.name,
              implementation: c.implementationName,
              protocol: c.protocol,
              enabled: c.enable,
              priority: c.priority,
              removeCompletedDownloads: c.removeCompletedDownloads,
              removeFailedDownloads: c.removeFailedDownloads,
              tags: c.tags,
            })),
          }, null, 2),
        }],
      };
    }
  • src/index.ts:136-142 (registration)
    Tool registration in addConfigTools function, creates 'radarr_get_download_clients' name via template string, defines description and empty input schema. Called when Radarr client is configured (line 176).
    name: `${serviceName}_get_download_clients`,
    description: `Get download client configurations from ${displayName}. Shows configured clients and their settings.`,
    inputSchema: {
      type: "object" as const,
      properties: {},
      required: [],
    },
  • Input schema definition for the tool: empty object (no parameters required).
    name: `${serviceName}_get_download_clients`,
    description: `Get download client configurations from ${displayName}. Shows configured clients and their settings.`,
    inputSchema: {
      type: "object" as const,
      properties: {},
      required: [],
    },
  • ArrClient.getDownloadClients() method: makes authenticated API request to /downloadclient endpoint, returns DownloadClient[] array. Inherited by RadarrClient.
     */
    async getDownloadClients(): Promise<DownloadClient[]> {
      return this.request<DownloadClient[]>('/downloadclient');
    }
  • TypeScript interface defining the structure of DownloadClient objects returned from the *arr API and used in handler response.
    export interface DownloadClient {
      id: number;
      name: string;
      implementation: string;
      implementationName: string;
      configContract: string;
      enable: boolean;
      protocol: string;
      priority: number;
      removeCompletedDownloads: boolean;
      removeFailedDownloads: boolean;
      fields: Array<{
        name: string;
        value: unknown;
      }>;
      tags: number[];
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool 'shows configured clients and their settings,' implying a read-only operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error handling, or whether it returns all clients at once. This is inadequate for a tool with zero annotation coverage.

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?

The description is a single, efficient sentence that front-loads the key action and resource. It avoids waste by not repeating the tool name or title, though it could be slightly more structured (e.g., by explicitly stating it's a read operation).

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the return values include (e.g., format, fields like client names or settings), behavioral aspects like permissions or side effects, or how it fits into broader workflows with sibling tools. For a tool with no structured data support, this leaves significant gaps.

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 has 0 parameters with 100% schema description coverage, so no parameter information is needed in the description. The description appropriately focuses on the tool's purpose without redundant parameter details, earning a baseline score of 4 for not adding unnecessary information.

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 states the action ('Get download client configurations') and resource ('from Radarr (Movies)'), specifying it retrieves configured clients and their settings. It distinguishes from siblings like radarr_get_movies or radarr_get_queue by focusing on download clients, though it doesn't explicitly contrast with lidarr_get_download_clients or similar tools.

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?

No guidance is provided on when to use this tool versus alternatives. While the description implies it's for viewing download client settings, it doesn't mention when to choose this over other Radarr tools (e.g., for setup vs. monitoring) or how it relates to sibling tools like radarr_review_setup or prowlarr_get_indexers, leaving usage context unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aplaceforallmystuff/mcp-arr'

If you have feedback or need assistance with the MCP directory API, please join our Discord server