Skip to main content
Glama

readarr_get_download_clients

Retrieve configured download client settings from Readarr for managing book downloads. View client configurations and their parameters.

Instructions

Get download client configurations from Readarr (Books). Shows configured clients and their settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary MCP tool handler for readarr_get_download_clients (shared with other services). Extracts service name, retrieves ReadarrClient instance, calls getDownloadClients(), formats and returns the list of download clients.
    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-143 (registration)
    Registers the 'readarr_get_download_clients' tool (when serviceName='readarr') in the TOOLS array with 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: [],
      },
    },
  • Core implementation of getDownloadClients() method in ArrClient base class (inherited by ReadarrClient). Makes authenticated API request to the /downloadclient endpoint.
    /**
     * Get download clients
     */
    async getDownloadClients(): Promise<DownloadClient[]> {
      return this.request<DownloadClient[]>('/downloadclient');
    }
  • TypeScript interface defining the structure of DownloadClient objects 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:79-81 (registration)
    Initializes the ReadarrClient instance if READARR_URL and READARR_API_KEY are set, making it available for tool handlers.
    case 'readarr':
      clients.readarr = new ReadarrClient(config);
      break;
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does ('Shows configured clients and their settings') but lacks critical details: whether this is a read-only operation, if it requires authentication, potential rate limits, error conditions, or the format/structure of returned data. For a tool with zero annotation coverage, this leaves significant gaps.

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 efficiently structured in two clear sentences: the first states the core purpose, the second elaborates on what's shown. Every word contributes meaning without redundancy, making it easy to parse and understand 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 output schema, no annotations), the description adequately covers the basic purpose. However, it lacks behavioral context that would be helpful for an agent (e.g., whether this is a safe read operation, what the output looks like). For a configuration retrieval tool, more detail about the nature of the data returned would improve completeness.

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 the schema fully documents the absence of inputs. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose. Baseline for 0 parameters is 4, as no parameter explanation is needed.

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 Readarr (Books)'), specifying it retrieves configured clients and their settings. It distinguishes from siblings by focusing on download clients specifically, though it doesn't explicitly contrast with similar tools like lidarr_get_download_clients or radarr_get_download_clients.

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 prerequisites, typical use cases, or differentiate from sibling tools that might serve similar purposes in other *arr applications (e.g., lidarr_get_download_clients for music).

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