Skip to main content
Glama

sonarr_get_download_clients

Retrieve configured download client settings from Sonarr to manage TV show downloads and monitor download progress.

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:136-143 (registration)
    Registration and schema definition for the sonarr_get_download_clients tool (dynamically generated with serviceName='sonarr' in addConfigTools function). Defines name, description, and empty input schema.
      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: [],
      },
    },
  • Primary handler logic for executing sonarr_get_download_clients. Dispatches to SonarrClient.getDownloadClients(), processes results, and returns formatted JSON response.
    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),
        }],
      };
    }
  • Core implementation in ArrClient base class: makes API request to /downloadclient endpoint to fetch download client configurations.
    async getDownloadClients(): Promise<DownloadClient[]> {
      return this.request<DownloadClient[]>('/downloadclient');
    }
  • TypeScript interface defining the structure of download client data returned by the API.
    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[];
    }
  • src/index.ts:174-176 (registration)
    Explicit registration call for Sonarr config tools, including sonarr_get_download_clients.
    // Add config tools for each configured service (except Prowlarr which has different config)
    if (clients.sonarr) addConfigTools('sonarr', 'Sonarr (TV)');
    if (clients.radarr) addConfigTools('radarr', 'Radarr (Movies)');
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,' which implies a read-only operation, but doesn't disclose behavioral traits like whether it requires authentication, rate limits, error handling, or the format of returned data. This is inadequate for a tool with no 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences that efficiently convey the tool's purpose and output. It's front-loaded with the main action and avoids unnecessary details, making it easy to parse quickly.

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?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is minimally adequate. It explains what the tool does but lacks details on behavioral aspects like authentication or data format. For a read operation with no complex inputs, it's passable but could be more informative.

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, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but that's appropriate here. A baseline of 4 is given as it meets expectations for a parameterless tool.

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 tool's purpose: 'Get download client configurations from Sonarr (TV).' It specifies the verb ('Get'), resource ('download client configurations'), and system context ('Sonarr (TV)'). However, it doesn't explicitly differentiate from sibling tools like 'lidarr_get_download_clients' or 'radarr_get_download_clients' beyond mentioning Sonarr, which is implied by the tool name.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, exclusions, or comparisons to similar tools (e.g., other 'get_download_clients' tools for different media systems). The context is clear but lacks explicit usage instructions.

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