Skip to main content
Glama

radarr_get_naming

Retrieve file and folder naming patterns from Radarr to configure how movies are organized in your media library.

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:144-152 (registration)
    Dynamically registers the 'radarr_get_naming' tool schema (input: empty object) when Radarr is configured, as part of addConfigTools('radarr', 'Radarr (Movies)') called at line 176.
    {
      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: [],
      },
    },
  • MCP tool handler dispatcher for 'radarr_get_naming': extracts service name, gets RadarrClient instance, calls getNamingConfig(), and returns JSON response.
    case "radarr_get_naming":
    case "lidarr_get_naming":
    case "readarr_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),
        }],
      };
    }
  • Core implementation in ArrClient (inherited by RadarrClient): fetches naming configuration via API GET /api/v3/config/naming on the Radarr server.
    async getNamingConfig(): Promise<NamingConfig> {
      return this.request<NamingConfig>('/config/naming');
    }
  • TypeScript interface defining the structure of the naming configuration returned by the Radarr API.
    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;
      // Readarr
      renameBooks?: boolean;
      authorFolderFormat?: string;
      bookFolderFormat?: string;
      standardBookFormat?: string;
    }
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 states the tool retrieves configuration ('Shows naming patterns'), implying a read-only operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or what happens if no configuration exists. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 two concise sentences that directly state the tool's purpose and what it shows. It's front-loaded with the core action ('Get file naming configuration') and avoids unnecessary details. Every sentence earns its place by clarifying the scope and output.

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 0 parameters, no annotations, and no output schema, the description is minimally adequate. It explains what the tool does but lacks details on the return format (e.g., structure of naming patterns), error handling, or integration with sibling tools. For a configuration retrieval tool, more context on output behavior would be helpful, but the description meets basic requirements.

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 tool has 0 parameters, and schema description coverage is 100%. The description doesn't need to explain parameters, and it appropriately doesn't mention any. It focuses on the tool's purpose without redundant parameter information, which is efficient given the empty input schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get file naming configuration from Radarr (Movies).' It specifies the verb ('Get'), resource ('file naming configuration'), and domain context ('Radarr (Movies)'). However, it doesn't explicitly differentiate from its sibling 'radarr_get_naming' (which appears to be the same tool based on the list) or other naming-related tools like 'trash_get_naming' or 'sonarr_get_naming'.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, conditions for use, or comparisons with sibling tools like 'trash_get_naming' or other Radarr configuration tools. The agent must infer usage from the tool name and description alone.

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