Skip to main content
Glama

trash_list_profiles

Lists recommended TRaSH Guides quality profiles for Radarr or Sonarr, showing optimal settings for different media types like 1080p, 4K, and Remux.

Instructions

List available TRaSH Guides quality profiles for Radarr or Sonarr. Shows recommended profiles for different use cases (1080p, 4K, Remux, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceYesWhich service to get profiles for

Implementation Reference

  • Core handler function in TrashClient class that lists available TRaSH quality profiles for a service by fetching from GitHub API or cache, including descriptions.
    async listProfiles(service: TrashService): Promise<{ name: string; description?: string }[]> {
      // Check cache
      const cached = cache.getProfileList(service);
      if (cached) {
        // Fetch details for each
        const profiles = await Promise.all(
          cached.map(name => this.getProfile(service, name))
        );
        return profiles.filter((p): p is TrashQualityProfile => p !== null).map(p => ({
          name: p.name,
          description: p.trash_description,
        }));
      }
    
      // Fetch list from GitHub
      const profileNames = await listGitHubDir(`${service}/quality-profiles`);
      cache.setProfileList(service, profileNames);
    
      // Fetch details
      const profiles = await Promise.all(
        profileNames.map(name => this.getProfile(service, name))
      );
      return profiles.filter((p): p is TrashQualityProfile => p !== null).map(p => ({
        name: p.name,
        description: p.trash_description,
      }));
    }
  • MCP server tool handler that calls trashClient.listProfiles and formats the response as MCP content.
    case "trash_list_profiles": {
      const service = (args as { service: TrashService }).service;
      const profiles = await trashClient.listProfiles(service);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            service,
            count: profiles.length,
            profiles: profiles.map(p => ({
              name: p.name,
              description: p.description?.replace(/<br>/g, ' ') || 'No description',
            })),
            usage: "Use trash_get_profile to see full details for a specific profile",
          }, null, 2),
        }],
      };
    }
  • src/index.ts:600-613 (registration)
    Tool registration in TOOLS array, including name, description, and input schema.
      name: "trash_list_profiles",
      description: "List available TRaSH Guides quality profiles for Radarr or Sonarr. Shows recommended profiles for different use cases (1080p, 4K, Remux, etc.)",
      inputSchema: {
        type: "object" as const,
        properties: {
          service: {
            type: "string",
            enum: ["radarr", "sonarr"],
            description: "Which service to get profiles for",
          },
        },
        required: ["service"],
      },
    },
  • Input schema definition for the trash_list_profiles tool, specifying the required 'service' parameter.
    inputSchema: {
      type: "object" as const,
      properties: {
        service: {
          type: "string",
          enum: ["radarr", "sonarr"],
          description: "Which service to get profiles for",
        },
      },
      required: ["service"],
    },
  • Singleton instance of TrashClient exported and used by the tool handler.
    export const trashClient = new TrashClient();
Behavior2/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 mentions that the tool 'Shows recommended profiles for different use cases', which implies a read-only operation, but does not specify if it requires authentication, has rate limits, or details the return format. This leaves gaps in understanding the tool's behavior beyond basic functionality.

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, consisting of two concise sentences that directly state the tool's purpose and key features. Every sentence adds value without redundancy, making it efficient and easy to understand.

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's low complexity (one parameter with full schema coverage) and no output schema, the description is moderately complete. It explains what the tool does and its use cases but lacks details on behavioral aspects like authentication or response format, which could be important for an AI agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'service' parameter fully documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as explaining the significance of choosing 'radarr' vs 'sonarr'. Since schema coverage is high, the baseline score of 3 is appropriate.

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 ('List') and resource ('available TRaSH Guides quality profiles for Radarr or Sonarr'), specifying what the tool does. It distinguishes itself from sibling tools like 'lidarr_get_quality_profiles' and 'radarr_get_quality_profiles' by focusing on TRaSH Guides profiles rather than general quality profiles, providing specific differentiation.

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

Usage Guidelines4/5

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

The description provides clear context by mentioning 'for Radarr or Sonarr' and 'Shows recommended profiles for different use cases (1080p, 4K, Remux, etc.)', indicating when to use this tool. However, it does not explicitly state when not to use it or name alternatives, such as 'trash_get_profile' or 'trash_compare_profile', which could help in sibling differentiation.

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