Skip to main content
Glama

sonarr_get_quality_profiles

Retrieve quality profiles from Sonarr including allowed qualities, upgrade settings, and custom format scores.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:132-142 (registration)
    Tool registration: sonarr_get_quality_profiles is dynamically created by addConfigTools('sonarr', 'Sonarr (TV)') on line 201. The tool name is generated via template literal `${serviceName}_get_quality_profiles` with inputSchema requiring no arguments.
    function addConfigTools(serviceName: string, displayName: string) {
      TOOLS.push(
        {
          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: [],
          },
        },
  • Input schema for sonarr_get_quality_profiles: empty object with no required properties (no arguments needed).
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • Handler for sonarr_get_quality_profiles: Extracts 'sonarr' from the tool name, gets the SonarrClient, calls client.getQualityProfiles() (which maps to GET /api/v3/qualityprofile), and returns a formatted response with profile details including allowed qualities, custom format scores, upgrade settings, and cutoff information.
    case "sonarr_get_quality_profiles":
    case "radarr_get_quality_profiles":
    case "lidarr_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),
        }],
      };
    }
  • Base API method getQualityProfiles() on ArrClient class that calls GET /api/v3/qualityprofile. Returns QualityProfile[] which is the data source for the tool handler.
    }
    
    /**
     * Get quality profiles
     */
    async getQualityProfiles(): Promise<QualityProfile[]> {
      return this.request<QualityProfile[]>('/qualityprofile');
    }
  • QualityProfile interface definition showing the data structure returned by the API: id, name, upgradeAllowed, cutoff, items (with quality info and allowed flag), formatItems, minFormatScore, cutoffFormatScore.
    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;
      }>;
    }
Behavior3/5

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

With no annotations, the description must cover behavioral traits. It states that the tool retrieves quality profiles and lists output elements, but does not mention safety (e.g., read-only nature), authentication needs, or any side effects. Basic transparency is present but lacks depth.

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, front-loaded sentence that conveys the core function and output details with no redundant words. Every part is necessary and efficiently structured.

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?

Despite lacking an output schema, the description adequately explains what the tool returns. It covers the key aspects (allowed qualities, upgrade settings, custom format scores). However, it could be more structured or mention the format (e.g., JSON) or typical use cases.

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 zero parameters, so the description carries the full burden. It explains the output content in detail, adding meaning beyond the empty schema. This meets the baseline of 4 for zero-parameter tools.

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 action ('Get'), the resource ('quality profiles'), and the context ('from Sonarr (TV)'), distinguishing it from similar tools for other services like Lidarr or Radarr. It also specifies the content returned: allowed qualities, upgrade settings, and custom format scores.

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?

No guidance is provided on when to use this tool versus alternatives among the many sibling tools. There is no mention of use cases, prerequisites, or scenarios that would make this tool the preferred choice.

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