Skip to main content
Glama

lidarr_review_setup

Analyze Lidarr music management configuration to identify issues and optimize quality profiles, download clients, naming rules, and storage settings.

Instructions

Get comprehensive configuration review for Lidarr (Music). Returns all settings for analysis: quality profiles, download clients, naming, storage, indexers, health warnings, and more. Use this to analyze the setup and suggest improvements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for lidarr_review_setup (and similar for other services): Fetches comprehensive configuration data from Lidarr including status, health checks, quality profiles, root folders, download clients, naming config, indexers, and metadata profiles (Lidarr-specific), then structures and returns it as JSON.
    case "sonarr_review_setup":
    case "radarr_review_setup":
    case "lidarr_review_setup":
    case "readarr_review_setup": {
      const serviceName = name.split('_')[0] as keyof typeof clients;
      const client = clients[serviceName];
      if (!client) throw new Error(`${serviceName} not configured`);
    
      // Gather all configuration data
      const [status, health, qualityProfiles, qualityDefinitions, downloadClients, naming, mediaManagement, rootFolders, tags, indexers] = await Promise.all([
        client.getStatus(),
        client.getHealth(),
        client.getQualityProfiles(),
        client.getQualityDefinitions(),
        client.getDownloadClients(),
        client.getNamingConfig(),
        client.getMediaManagement(),
        client.getRootFoldersDetailed(),
        client.getTags(),
        client.getIndexers(),
      ]);
    
      // For Lidarr/Readarr, also get metadata profiles
      let metadataProfiles = null;
      if (serviceName === 'lidarr' && clients.lidarr) {
        metadataProfiles = await clients.lidarr.getMetadataProfiles();
      } else if (serviceName === 'readarr' && clients.readarr) {
        metadataProfiles = await clients.readarr.getMetadataProfiles();
      }
    
      const review = {
        service: serviceName,
        version: status.version,
        appName: status.appName,
        platform: {
          os: status.osName,
          isDocker: status.isDocker,
        },
        health: {
          issueCount: health.length,
          issues: health,
        },
        storage: {
          rootFolders: rootFolders.map(f => ({
            path: f.path,
            accessible: f.accessible,
            freeSpace: formatBytes(f.freeSpace),
            freeSpaceBytes: f.freeSpace,
            unmappedFolderCount: f.unmappedFolders?.length || 0,
          })),
        },
        qualityProfiles: qualityProfiles.map(p => ({
          id: p.id,
          name: p.name,
          upgradeAllowed: p.upgradeAllowed,
          cutoff: p.cutoff,
          allowedQualities: p.items
            .filter(i => i.allowed)
            .map(i => i.quality?.name || i.name || (i.items?.map(q => q.quality.name).join(', ')))
            .filter(Boolean),
          customFormatsWithScores: p.formatItems?.filter(f => f.score !== 0).length || 0,
          minFormatScore: p.minFormatScore,
        })),
        qualityDefinitions: qualityDefinitions.map(d => ({
          quality: d.quality.name,
          minSize: d.minSize + ' MB/min',
          maxSize: d.maxSize === 0 ? 'unlimited' : d.maxSize + ' MB/min',
          preferredSize: d.preferredSize + ' MB/min',
        })),
        downloadClients: downloadClients.map(c => ({
          name: c.name,
          type: c.implementationName,
          protocol: c.protocol,
          enabled: c.enable,
          priority: c.priority,
        })),
        indexers: indexers.map(i => ({
          name: i.name,
          protocol: i.protocol,
          enableRss: i.enableRss,
          enableAutomaticSearch: i.enableAutomaticSearch,
          enableInteractiveSearch: i.enableInteractiveSearch,
          priority: i.priority,
        })),
        naming: naming,
        mediaManagement: {
          recycleBin: mediaManagement.recycleBin || 'not set',
          recycleBinCleanupDays: mediaManagement.recycleBinCleanupDays,
          downloadPropersAndRepacks: mediaManagement.downloadPropersAndRepacks,
          deleteEmptyFolders: mediaManagement.deleteEmptyFolders,
          copyUsingHardlinks: mediaManagement.copyUsingHardlinks,
          importExtraFiles: mediaManagement.importExtraFiles,
          extraFileExtensions: mediaManagement.extraFileExtensions,
        },
        tags: tags.map(t => t.label),
        ...(metadataProfiles && { metadataProfiles }),
      };
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify(review, null, 2),
        }],
      };
    }
  • src/index.ts:163-170 (registration)
    Registration of lidarr_review_setup tool: Dynamically adds the tool to the TOOLS array with name 'lidarr_review_setup', description, and empty input schema via addConfigTools('lidarr', 'Lidarr (Music)') called at line 177.
      name: `${serviceName}_review_setup`,
      description: `Get comprehensive configuration review for ${displayName}. Returns all settings for analysis: quality profiles, download clients, naming, storage, indexers, health warnings, and more. Use this to analyze the setup and suggest improvements.`,
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    }
  • src/index.ts:177-178 (registration)
    Conditional registration: Adds Lidarr-specific tools including lidarr_review_setup only if Lidarr client is configured.
    if (clients.lidarr) addConfigTools('lidarr', 'Lidarr (Music)');
    if (clients.readarr) addConfigTools('readarr', 'Readarr (Books)');
  • Helper function formatBytes used in the review handler to format free space and sizes in human-readable form.
    function formatBytes(bytes: number): string {
      if (bytes === 0) return '0 B';
      const k = 1024;
      const sizes = ['B', 'KB', 'MB', 'GB', 'TB'];
      const i = Math.floor(Math.log(bytes) / Math.log(k));
      return parseFloat((bytes / Math.pow(k, i)).toFixed(2)) + ' ' + sizes[i];
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool as a read operation ('Get comprehensive configuration review') and specifies the scope of data returned, which is helpful. However, it doesn't mention potential side effects, authentication requirements, rate limits, or response format details. The description adds value by clarifying the comprehensive nature of the review but lacks depth on behavioral traits.

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 appropriately sized and front-loaded, with two sentences that efficiently convey the tool's purpose and usage. The first sentence defines what it does and what it returns, and the second sentence provides clear usage guidance. There is no wasted language or redundancy, making it easy for an AI agent to parse and understand quickly.

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

Completeness4/5

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

Given the tool's complexity (a comprehensive configuration review tool with no parameters) and the absence of annotations and output schema, the description is reasonably complete. It explains the tool's purpose, scope of returned data, and when to use it. However, it doesn't detail the output structure or potential limitations, which could be helpful since there's no output schema. For a read-only tool with no parameters, this is mostly adequate but could be slightly enhanced with output details.

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 the schema fully documents the lack of parameters. The description appropriately doesn't add parameter details, as none are needed. It focuses on the tool's purpose and output scope instead, which is correct for a parameterless tool. The baseline for 0 parameters is 4, as the description compensates by explaining what the tool does without unnecessary parameter information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 with specific verbs ('Get comprehensive configuration review') and resources ('Lidarr (Music)'), and distinguishes it from sibling tools by emphasizing its comprehensive nature versus the more specific sibling tools like lidarr_get_quality_profiles or lidarr_get_naming. It explicitly mentions returning 'all settings for analysis' including quality profiles, download clients, naming, storage, indexers, health warnings, and more.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool: 'Use this to analyze the setup and suggest improvements.' This clearly indicates its purpose is for configuration review and optimization analysis, distinguishing it from sibling tools that perform specific queries or operations like lidarr_get_albums or lidarr_search. It implies an alternative to using multiple specific tools for a holistic review.

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