Skip to main content
Glama

lidarr_get_naming

Retrieve file and folder naming patterns from Lidarr for consistent music library organization.

Instructions

Get file naming configuration from Lidarr (Music). Shows naming patterns for files and folders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:144-152 (registration)
    Registration of the lidarr_get_naming tool (via dynamic `${serviceName}_get_naming`) in the addConfigTools function, including its schema with no input parameters.
    {
      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:177-177 (registration)
    Invocation of addConfigTools for Lidarr service, which registers the lidarr_get_naming tool if Lidarr client is configured.
    if (clients.lidarr) addConfigTools('lidarr', 'Lidarr (Music)');
  • TypeScript interface defining the structure of the naming configuration data returned by the tool.
    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;
    }
  • Main handler for lidarr_get_naming tool call: parses service name from tool name, retrieves LidarrClient instance, calls getNamingConfig(), and returns the result as formatted JSON text.
    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),
        }],
      };
    }
  • Implementation of getNamingConfig method in base ArrClient (used by LidarrClient): performs HTTP GET request to /api/{apiVersion}/config/naming endpoint to fetch the naming configuration.
    /**
     * Get naming configuration
     */
    async getNamingConfig(): Promise<NamingConfig> {
      return this.request<NamingConfig>('/config/naming');
    }
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 ('Get', 'Shows'), implying a read-only operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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: two concise sentences that directly state the tool's purpose without unnecessary details. Every sentence earns its place by clarifying the resource and what it shows. There's zero waste or redundancy.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It explains what the tool does but lacks context on behavioral aspects like authentication or response format. For a read-only configuration tool, it's complete enough to understand the basic purpose but could benefit from additional operational details.

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 with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter semantics, and it doesn't incorrectly suggest any parameters. A baseline of 4 is appropriate as the description doesn't contradict the schema and the schema handles parameter documentation completely.

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 Lidarr (Music). Shows naming patterns for files and folders.' It specifies the verb ('Get'), resource ('file naming configuration'), and scope ('from Lidarr (Music)'), distinguishing it from generic configuration tools. However, it doesn't explicitly differentiate from sibling naming tools like radarr_get_naming or sonarr_get_naming beyond mentioning 'Lidarr (Music)'.

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 sibling tools (e.g., radarr_get_naming for movies, sonarr_get_naming for TV shows) or clarify use cases like configuration review versus setup. Usage is implied by the tool name but not explicitly stated.

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