Skip to main content
Glama

radarr_review_setup

Analyze Radarr movie management configuration to identify issues and optimize settings for quality profiles, download clients, naming, storage, and indexers.

Instructions

Get comprehensive configuration review for Radarr (Movies). 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

  • src/index.ts:163-170 (registration)
    Tool registration and schema definition for generic {service}_review_setup (instantiated as radarr_review_setup when serviceName='radarr') added to TOOLS array.
      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:176-176 (registration)
    Conditional invocation of addConfigTools('radarr') which registers the radarr_review_setup tool if Radarr client is configured.
    if (clients.radarr) addConfigTools('radarr', 'Radarr (Movies)');
  • Main handler logic for radarr_review_setup tool. Extracts service name, fetches all relevant configuration data using RadarrClient methods, assembles and returns a structured JSON review of the setup.
    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),
        }],
      };
    }
  • RadarrClient class providing API client methods (inherits from ArrClient which implements getStatus, getHealth, getQualityProfiles, etc. used by the review handler).
    export class RadarrClient extends ArrClient {
      constructor(config: ArrConfig) {
        super('radarr', config);
      }
    
      /**
       * Get all movies
       */
      async getMovies(): Promise<Movie[]> {
        return this['request']<Movie[]>('/movie');
      }
    
      /**
       * Get a specific movie
       */
      async getMovieById(id: number): Promise<Movie> {
        return this['request']<Movie>(`/movie/${id}`);
      }
    
      /**
       * Search for movies
       */
      async searchMovies(term: string): Promise<SearchResult[]> {
        return this['request']<SearchResult[]>(`/movie/lookup?term=${encodeURIComponent(term)}`);
      }
    
      /**
       * Add a movie
       */
      async addMovie(movie: Partial<Movie> & { tmdbId: number; rootFolderPath: string; qualityProfileId: number }): Promise<Movie> {
        return this['request']<Movie>('/movie', {
          method: 'POST',
          body: JSON.stringify({
            ...movie,
            monitored: movie.monitored ?? true,
            addOptions: {
              searchForMovie: true,
            },
          }),
        });
      }
    
      /**
       * Trigger a search for a movie
       */
      async searchMovie(movieId: number): Promise<{ id: number }> {
        return this['request']<{ id: number }>('/command', {
          method: 'POST',
          body: JSON.stringify({
            name: 'MoviesSearch',
            movieIds: [movieId],
          }),
        });
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the tool returns settings for analysis but doesn't disclose behavioral traits like whether it's read-only, requires authentication, has rate limits, or what happens on errors. For a tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is two sentences, front-loaded with the main purpose and followed by usage context. It's efficient with minimal waste, though the second sentence could be more tightly integrated. Overall, it's appropriately sized for the tool's complexity.

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 no annotations and no output schema, the description provides basic purpose and usage but lacks details on return format, error handling, or behavioral constraints. For a tool that returns 'all settings for analysis', more context on output structure would be helpful, but it's minimally adequate for a read operation.

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 lack of inputs. The description adds no parameter information, which is appropriate here. Baseline is 4 for zero parameters as it doesn't need to compensate for schema gaps.

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 comprehensive configuration review for Radarr (Movies)' with specific verb ('Get') and resource ('configuration review'), and lists key components like quality profiles, download clients, etc. It distinguishes from siblings by focusing on comprehensive review rather than specific components, though it doesn't explicitly name alternatives.

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

Usage Guidelines3/5

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

The description implies usage context ('to analyze the setup and suggest improvements') but doesn't explicitly state when to use this tool versus sibling tools like radarr_get_quality_profiles or radarr_get_naming. It suggests the tool is for analysis but lacks clear alternatives or exclusions.

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