Skip to main content
Glama

lidarr_get_quality_profiles

Retrieve music quality profiles from Lidarr to view allowed formats, upgrade rules, and custom format scoring for media management.

Instructions

Get detailed quality profiles from Lidarr (Music). Shows allowed qualities, upgrade settings, and custom format scores.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:174-179 (registration)
    Registration of configuration tools for Lidarr (among others) by calling addConfigTools if Lidarr client is configured, adding 'lidarr_get_quality_profiles' to the TOOLS array.
    // 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)');
    if (clients.lidarr) addConfigTools('lidarr', 'Lidarr (Music)');
    if (clients.readarr) addConfigTools('readarr', 'Readarr (Books)');
  • Tool schema definition for *_get_quality_profiles (used for lidarr_get_quality_profiles) within addConfigTools function: name, description, empty input schema.
    {
      name: `${serviceName}_get_quality_profiles`,
      description: `Get detailed quality profiles from ${displayName}. Shows allowed qualities, upgrade settings, and custom format scores.`,
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • Main handler logic for lidarr_get_quality_profiles: parses service name, retrieves Lidarr client, calls getQualityProfiles(), formats output with count, profile summaries, allowed qualities, and custom format scores.
    case "sonarr_get_quality_profiles":
    case "radarr_get_quality_profiles":
    case "lidarr_get_quality_profiles":
    case "readarr_get_quality_profiles": {
      const serviceName = name.split('_')[0] as keyof typeof clients;
      const client = clients[serviceName];
      if (!client) throw new Error(`${serviceName} not configured`);
      const profiles = await client.getQualityProfiles();
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: profiles.length,
            profiles: profiles.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),
              customFormats: p.formatItems?.filter(f => f.score !== 0).map(f => ({
                name: f.name,
                score: f.score,
              })) || [],
              minFormatScore: p.minFormatScore,
              cutoffFormatScore: p.cutoffFormatScore,
            })),
          }, null, 2),
        }],
      };
    }
  • Core helper method getQualityProfiles() in ArrClient (inherited by LidarrClient) that makes API request to /qualityprofile endpoint.
     */
    async getQualityProfiles(): Promise<QualityProfile[]> {
      return this.request<QualityProfile[]>('/qualityprofile');
    }
  • TypeScript interface defining QualityProfile structure used by getQualityProfiles() response.
    export interface QualityProfile {
      id: number;
      name: string;
      upgradeAllowed: boolean;
      cutoff: number;
      items: Array<{
        id?: number;
        name?: string;
        quality?: { id: number; name: string; source: string; resolution: number };
        items?: Array<{ quality: { id: number; name: string } }>;
        allowed: boolean;
      }>;
      minFormatScore: number;
      cutoffFormatScore: number;
      formatItems: Array<{
        format: number;
        name: string;
        score: 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 the tool 'shows' information, which suggests a read-only operation, but does not disclose behavioral traits such as authentication requirements, rate limits, or error handling. For a tool with zero annotation coverage, this lack of detail is a significant gap.

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 a single, well-structured sentence that front-loads the purpose and lists key details without waste. Every word earns its place, making it highly concise and clear.

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 is minimal but adequate for a simple read operation. However, it lacks details on output format or behavioral context, which could be helpful for an AI agent. It meets basic needs but has room for improvement in 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add param info, which is appropriate here. Baseline is 4 for 0 params, as it efficiently avoids redundancy.

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 verb ('Get'), resource ('detailed quality profiles from Lidarr'), and scope ('Music'), specifying it shows 'allowed qualities, upgrade settings, and custom format scores.' It distinguishes from siblings like lidarr_get_albums or lidarr_get_artists by focusing on quality profiles, making the purpose specific and well-defined.

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 for retrieving quality profile details in Lidarr, but does not explicitly state when to use this tool versus alternatives like radarr_get_quality_profiles or sonarr_get_quality_profiles for other media types. No guidance on prerequisites or exclusions is provided, leaving usage context somewhat implied rather than explicit.

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