Skip to main content
Glama

radarr_get_naming

Retrieve file naming configuration from Radarr for movies. Shows naming patterns for both files and folders.

Instructions

Get file naming configuration from Radarr (Movies). Shows naming patterns for files and folders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:170-178 (registration)
    Tool 'radarr_get_naming' is registered dynamically via addConfigTools() when clients.radarr is configured. The function creates a tool with name `${serviceName}_get_naming` (line 171), schema with no required params (lines 173-177), and description about file naming configuration (line 172).
    {
      name: `${serviceName}_get_naming`,
      description: `Get file naming configuration from ${displayName}. Shows naming patterns for files and folders.`,
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • The handler for 'radarr_get_naming' (and similarly 'sonarr_get_naming', 'lidarr_get_naming') is in the switch/case at lines 1300-1313. It extracts the service name from the tool name, gets the client, calls client.getNamingConfig(), and returns the naming configuration as JSON.
    // Naming config
    case "sonarr_get_naming":
    case "radarr_get_naming":
    case "lidarr_get_naming": {
      const serviceName = name.split('_')[0] as keyof typeof clients;
      const client = clients[serviceName];
      if (!client) throw new Error(`${serviceName} not configured`);
      const naming = await client.getNamingConfig();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(naming, null, 2),
        }],
      };
    }
  • The getNamingConfig() method on the base ArrClient class (line 493) makes a GET request to '/config/naming' and returns a NamingConfig object. This is inherited by RadarrClient and all other service clients.
    /**
     * Get naming configuration
     */
    async getNamingConfig(): Promise<NamingConfig> {
      return this.request<NamingConfig>('/config/naming');
    }
  • The NamingConfig interface (lines 286-306) defines the shape of the naming configuration returned by getNamingConfig(). It includes fields like renameMovies, movieFolderFormat, standardMovieFormat (for Radarr), and renameEpisodes, seriesFolderFormat etc. (for Sonarr/Lidarr).
    export interface NamingConfig {
      renameEpisodes?: boolean;
      replaceIllegalCharacters: boolean;
      colonReplacementFormat?: string;
      standardEpisodeFormat?: string;
      dailyEpisodeFormat?: string;
      animeEpisodeFormat?: string;
      seriesFolderFormat?: string;
      seasonFolderFormat?: string;
      specialsFolderFormat?: string;
      multiEpisodeStyle?: number;
      // Radarr
      renameMovies?: boolean;
      movieFolderFormat?: string;
      standardMovieFormat?: string;
      // Lidarr
      renameTracks?: boolean;
      artistFolderFormat?: string;
      albumFolderFormat?: string;
      trackFormat?: string;
    }
Behavior2/5

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

No annotations and minimal behavioral details; does not describe response format, potential errors, or authentication requirements beyond implied read-only operation.

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?

Single sentence, 16 words, front-loaded with core purpose, every word contributes value.

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?

Adequately covers output (naming patterns for files and folders) for a simple retrieval tool with no parameters, though could mention scope of naming.

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?

No parameters in schema, so description does not need to add parameter info; baseline is 4.

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 tool retrieves file naming configuration from Radarr for movies, using specific verb 'Get' and resource 'file naming configuration'.

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 on when to use this tool versus siblings like sonarr_get_naming or trash_get_naming, missing context on use cases.

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