Skip to main content
Glama

sonarr_get_download_clients

List all download clients configured in Sonarr with their settings to manage TV show downloads.

Instructions

Get download client configurations from Sonarr (TV). Shows configured clients and their settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:162-169 (registration)
    Tool registration for sonarr_get_download_clients (and radarr/lidarr variants) as a configuration tool added via addConfigTools(). The schema defines it as an object with no required parameters.
      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: [],
      },
    },
  • Handler for sonarr_get_download_clients (also radarr_get_download_clients and lidarr_get_download_clients). Extracts the service name from the tool name, calls client.getDownloadClients(), and returns formatted JSON with id, name, implementationName, protocol, enable, priority, removeCompletedDownloads, removeFailedDownloads, and tags.
    case "sonarr_get_download_clients":
    case "radarr_get_download_clients":
    case "lidarr_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),
        }],
      };
    }
  • The getDownloadClients() method on ArrClient class. Makes a GET request to /downloadclient endpoint and returns an array of DownloadClient objects.
    async getDownloadClients(): Promise<DownloadClient[]> {
      return this.request<DownloadClient[]>('/downloadclient');
    }
  • DownloadClient TypeScript interface defining the shape of download client data returned from the API, including id, name, implementationName, enable, protocol, priority, removeCompletedDownloads, removeFailedDownloads, tags, etc.
    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 provided, and the description only states it 'shows' configurations, implying read-only behavior but not explicitly stating safety, side effects, or authentication needs. Minimal behavioral disclosure beyond the obvious.

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?

Two concise sentences with no wasted words. Every sentence adds value: first states the function, second confirms the result.

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?

The description is adequate for a simple, parameterless tool, but lacks details about the return format or what 'settings' include. With no output schema, more completeness would be beneficial.

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 input schema has zero parameters, so schema description coverage is 100%. The description adds nothing about parameters, but baseline for zero parameters is 4, which 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?

The description clearly states the action ('Get') and resource ('download client configurations') specific to Sonarr (TV). While it doesn't explicitly differentiate from siblings like radarr_get_download_clients, the tool name and context suffice.

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 on when to use this tool versus alternatives, such as tools for other arrs. Since it has no parameters and is straightforward, some guidance would help, but it's missing.

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