Skip to main content
Glama

sonarr_get_naming

Retrieve file and folder naming patterns from Sonarr to configure how TV shows are organized in your media library.

Instructions

Get file naming configuration from Sonarr (TV). Shows naming patterns for files and folders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler dispatch for sonarr_get_naming: parses service from name, retrieves SonarrClient, calls getNamingConfig(), formats as JSON response.
    // Naming config
    case "sonarr_get_naming":
    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 of getNamingConfig in ArrClient base class (used by SonarrClient): API GET request to /api/v3/config/naming.
    /**
     * Get naming configuration
     */
    async getNamingConfig(): Promise<NamingConfig> {
      return this.request<NamingConfig>('/config/naming');
    }
  • TypeScript interface defining the NamingConfig response structure from Sonarr 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;
    }
  • src/index.ts:144-152 (registration)
    MCP Tool registration definition for sonarr_get_naming (dynamic via serviceName='sonarr'): name, description, empty input schema.
    {
      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: [],
      },
    },
  • src/index.ts:174-179 (registration)
    Conditional invocation of addConfigTools for Sonarr, which registers sonarr_get_naming tool.
    // Add config tools for each configured service (except Prowlarr which has different config)
    if (clients.sonarr) addConfigTools('sonarr', 'Sonarr (TV)');
    if (clients.radarr) addConfigTools('radarr', 'Radarr (Movies)');
    if (clients.lidarr) addConfigTools('lidarr', 'Lidarr (Music)');
    if (clients.readarr) addConfigTools('readarr', 'Readarr (Books)');
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 states the tool retrieves configuration ('Get...Shows naming patterns'), implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns structured data, or handles errors. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise and front-loaded: a single sentence clearly states the tool's purpose, and a second sentence elaborates on what it shows ('naming patterns for files and folders'). Every word earns its place with no redundancy or fluff.

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 (0 parameters, no output schema, no annotations), the description is minimally adequate. It explains what the tool does but lacks details on behavioral traits (e.g., authentication needs, return format) that would be helpful for an agent. Without annotations or output schema, more context on the response structure would improve completeness.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, and the baseline for 0 parameters is 4, as it avoids unnecessary details while matching the schema's simplicity.

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 Sonarr (TV)' specifies the verb ('Get'), resource ('file naming configuration'), and domain ('Sonarr (TV)'). It distinguishes from siblings like 'sonarr_get_series' by focusing on naming patterns, though it doesn't explicitly contrast with similar tools like 'trash_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 when this tool is appropriate (e.g., for configuration review) or when to choose other tools like 'trash_get_naming' or 'lidarr_get_naming', leaving usage context implied at best.

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