Skip to main content
Glama

trash_get_naming

Retrieve TRaSH Guides naming conventions for Radarr or Sonarr to organize media files for Plex, Emby, Jellyfin, or standard setups.

Instructions

Get TRaSH Guides recommended naming conventions for your media server (Plex, Emby, Jellyfin, or standard)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceYesWhich service
mediaServerYesWhich media server you use

Implementation Reference

  • Tool schema definition for 'trash_get_naming', specifying input parameters service (radarr/sonarr) and mediaServer (plex/emby/jellyfin/standard). Part of TOOLS array registration.
    name: "trash_get_naming",
    description: "Get TRaSH Guides recommended naming conventions for your media server (Plex, Emby, Jellyfin, or standard)",
    inputSchema: {
      type: "object" as const,
      properties: {
        service: {
          type: "string",
          enum: ["radarr", "sonarr"],
          description: "Which service",
        },
        mediaServer: {
          type: "string",
          enum: ["plex", "emby", "jellyfin", "standard"],
          description: "Which media server you use",
        },
      },
      required: ["service", "mediaServer"],
    },
  • MCP server handler for 'trash_get_naming' tool call. Extracts arguments, fetches data via trashClient.getNaming(service), maps media server variants, formats and returns recommended naming conventions.
    case "trash_get_naming": {
      const { service, mediaServer } = args as { service: TrashService; mediaServer: string };
      const naming = await trashClient.getNaming(service);
      if (!naming) {
        return {
          content: [{
            type: "text",
            text: JSON.stringify({ error: `Could not fetch naming conventions for ${service}` }, null, 2),
          }],
          isError: true,
        };
      }
    
      // Map media server to naming key
      const serverMap: Record<string, { folder: string; file: string }> = {
        plex: { folder: 'plex-imdb', file: 'plex-imdb' },
        emby: { folder: 'emby-imdb', file: 'emby-imdb' },
        jellyfin: { folder: 'jellyfin-imdb', file: 'jellyfin-imdb' },
        standard: { folder: 'default', file: 'standard' },
      };
    
      const keys = serverMap[mediaServer] || serverMap.standard;
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            service,
            mediaServer,
            recommended: {
              folder: naming.folder[keys.folder] || naming.folder.default,
              file: naming.file[keys.file] || naming.file.standard,
              ...(naming.season && { season: naming.season[keys.folder] || naming.season.default }),
              ...(naming.series && { series: naming.series[keys.folder] || naming.series.default }),
            },
            allFolderOptions: Object.keys(naming.folder),
            allFileOptions: Object.keys(naming.file),
          }, null, 2),
        }],
      };
    }
  • Core implementation of trashClient.getNaming(service): checks cache, fetches naming JSON from TRaSH Guides GitHub repo if needed, caches and returns TrashNaming data.
    async getNaming(service: TrashService): Promise<TrashNaming | null> {
      const cached = cache.getNaming(service);
      if (cached) return cached;
    
      try {
        const naming = await fetchJSON<TrashNaming>(
          `${TRASH_BASE_URL}/${service}/naming/${service}-naming.json`
        );
        cache.setNaming(service, naming);
        return naming;
      } catch {
        return null;
      }
    }
  • src/index.ts:750-752 (registration)
    Registration of all tools (including trash_get_naming) via ListToolsRequestSchema handler returning the TOOLS array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools: TOOLS };
    });
  • Singleton export of TrashClient instance used by the 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 full burden but only states what the tool does, not how it behaves. It doesn't disclose whether this is a read-only operation, if it requires authentication, rate limits, what format the recommendations come in, or any error conditions. For a tool with zero annotation coverage, this is insufficient behavioral disclosure.

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, efficient sentence that front-loads the core purpose with zero wasted words. Every element ('Get TRaSH Guides recommended naming conventions for your media server') directly contributes to understanding the tool's function.

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?

For a simple lookup tool with no annotations and no output schema, the description adequately explains what it does but lacks crucial context about return format, error handling, and behavioral constraints. Given the schema richness (100% coverage, enums), it's minimally viable but leaves significant gaps in understanding how to properly use the tool.

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 description mentions 'media server' which aligns with one parameter, but doesn't explain the 'service' parameter or why both are required. With 100% schema description coverage, the baseline is 3, and the description adds minimal value beyond what the schema already documents about parameter purposes.

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 specific action ('Get') and resource ('TRaSH Guides recommended naming conventions') with precise scope ('for your media server'). It distinguishes from siblings like 'trash_compare_naming' by focusing on retrieval rather than comparison, and from '*_get_naming' tools by specifying TRaSH Guides as the source.

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 for when to use this tool: when you need naming conventions for a media server (Plex, Emby, Jellyfin, or standard). However, it doesn't explicitly state when NOT to use it or name specific alternatives like 'trash_compare_naming' for comparison tasks, which would be needed for a perfect score.

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