Skip to main content
Glama

lidarr_get_download_clients

Retrieve configured download client settings from Lidarr to manage music downloads and monitor client status.

Instructions

Get download client configurations from Lidarr (Music). Shows configured clients and their settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for lidarr_get_download_clients (and similar tools): extracts service name, fetches LidarrClient instance, calls getDownloadClients(), formats and returns the list of download clients as JSON.
    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: defines the 'lidarr_get_download_clients' tool schema (empty input) and description, added to TOOLS array when Lidarr is configured.
    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 helper method in ArrClient (inherited by LidarrClient): makes API request to /downloadclient endpoint to fetch download clients.
     * Get download clients
     */
    async getDownloadClients(): Promise<DownloadClient[]> {
      return this.request<DownloadClient[]>('/downloadclient');
    }
  • src/index.ts:175-178 (registration)
    Conditional registration call: adds lidarr_get_download_clients (and other config tools) to TOOLS if Lidarr client is configured.
    if (clients.sonarr) addConfigTools('sonarr', 'Sonarr (TV)');
    if (clients.radarr) addConfigTools('radarr', 'Radarr (Movies)');
    if (clients.lidarr) addConfigTools('lidarr', 'Lidarr (Music)');
    if (clients.readarr) addConfigTools('readarr', 'Readarr (Books)');
  • Type definition for DownloadClient interface used in getDownloadClients 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 mentions 'Shows configured clients and their settings,' which implies a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or response format. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 scope. It's front-loaded with the main action and avoids unnecessary words, 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 has no parameters, no annotations, and no output schema, the description provides basic context but is incomplete. It doesn't explain what the output looks like (e.g., list format, data structure) or potential errors, which could hinder an AI agent's ability to use it effectively. However, for a simple read operation, it meets minimal viability.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. A baseline of 4 is applied as it adequately handles the lack of parameters without redundancy.

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 Lidarr (Music).' It specifies the verb ('Get'), resource ('download client configurations'), and context ('Lidarr (Music)'). However, it doesn't explicitly differentiate from sibling tools like 'radarr_get_download_clients' or 'sonarr_get_download_clients' beyond mentioning 'Lidarr' in parentheses.

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 sibling tools like 'lidarr_get_queue' or 'lidarr_search', nor does it specify prerequisites, such as needing Lidarr to be configured with download clients. Usage is implied by the name and description but not explicitly stated.

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