Skip to main content
Glama

lidarr_get_calendar

Retrieve upcoming album releases from Lidarr to plan music collection updates. Specify days ahead to view release schedules.

Instructions

Get upcoming album releases from Lidarr

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days to look ahead (default: 30)

Implementation Reference

  • Main handler for the lidarr_get_calendar tool. Checks if Lidarr client is configured, computes date range from input 'days' parameter (default 30), calls LidarrClient.getCalendar, formats response with album count and details.
    case "lidarr_get_calendar": {
      if (!clients.lidarr) throw new Error("Lidarr not configured");
      const days = (args as { days?: number })?.days || 30;
      const start = new Date().toISOString().split('T')[0];
      const end = new Date(Date.now() + days * 24 * 60 * 60 * 1000).toISOString().split('T')[0];
      const calendar = await clients.lidarr.getCalendar(start, end);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: calendar.length,
            albums: calendar.map(a => ({
              id: a.id,
              title: a.title,
              artistId: a.artistId,
              releaseDate: a.releaseDate,
              albumType: a.albumType,
              monitored: a.monitored,
            })),
          }, null, 2),
        }],
      };
    }
  • src/index.ts:423-436 (registration)
    Tool registration in TOOLS array (conditional on Lidarr client being configured). Defines the tool name, description, and input schema with optional 'days' parameter.
        name: "lidarr_get_calendar",
        description: "Get upcoming album releases from Lidarr",
        inputSchema: {
          type: "object" as const,
          properties: {
            days: {
              type: "number",
              description: "Number of days to look ahead (default: 30)",
            },
          },
          required: [],
        },
      }
    );
  • LidarrClient.getCalendar method: Constructs Lidarr API calendar endpoint with optional start/end dates, calls the base request method to fetch upcoming album releases.
    async getCalendar(start?: string, end?: string): Promise<Album[]> {
      const params = new URLSearchParams();
      if (start) params.append('start', start);
      if (end) params.append('end', end);
      const query = params.toString() ? `?${params.toString()}` : '';
      return this['request']<Album[]>(`/calendar${query}`);
    }
  • src/index.ts:76-78 (registration)
    Initialization of LidarrClient instance if LIDARR_URL and LIDARR_API_KEY env vars are set.
    case 'lidarr':
      clients.lidarr = new LidarrClient(config);
      break;
  • TypeScript interface defining the Album structure returned by Lidarr calendar API.
    export interface Album {
      id: number;
      title: string;
      disambiguation: string;
      overview: string;
      artistId: number;
      foreignAlbumId: string;
      monitored: boolean;
      anyReleaseOk: boolean;
      profileId: number;
      duration: number;
      albumType: string;
      genres: string[];
      images: Array<{ coverType: string; url: string }>;
      links: Array<{ url: string; name: string }>;
      statistics?: {
        trackFileCount: number;
        trackCount: number;
        totalTrackCount: number;
        sizeOnDisk: number;
        percentOfTracks: number;
      };
      releaseDate: string;
      releases: Array<{
        id: number;
        albumId: number;
        foreignReleaseId: string;
        title: string;
        status: string;
        duration: number;
        trackCount: number;
        monitored: boolean;
      }>;
      grabbed: boolean;
    }
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 provides minimal behavioral context. It doesn't mention whether this is a read-only operation, what format the results come in, whether there are rate limits, or any authentication requirements. The description only states what the tool does at a high level.

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 gets straight to the point with zero wasted words. It's perfectly front-loaded and appropriately sized for the tool's complexity.

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 read operation with one optional parameter and no output schema, the description is minimally adequate. However, it lacks important context about what the output looks like (album details, format, structure) and how it differs from similar tools, which would be helpful for an AI agent.

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 schema has 100% description coverage with a clear parameter description for 'days', so the baseline is 3. The tool description doesn't add any additional parameter information beyond what's already in the schema, but the schema documentation is complete for the single parameter.

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 action ('Get') and resource ('upcoming album releases from Lidarr'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling calendar tools like 'radarr_get_calendar' or 'sonarr_get_calendar' which follow the same pattern for different media types.

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 is provided about when to use this tool versus alternatives. There's no mention of how it differs from other search tools like 'lidarr_search' or 'lidarr_search_album', nor any indication of when calendar functionality is preferred over search functionality.

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