Skip to main content
Glama

radarr_get_calendar

Retrieve upcoming movie releases from Radarr for a specified number of days. Plan your media library updates in advance.

Instructions

Get upcoming movie releases from Radarr

Input Schema

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

Implementation Reference

  • The tool handler for 'radarr_get_calendar' in the CallToolRequestSchema switch statement. It checks Radarr is configured, extracts optional 'days' parameter (default 30), computes ISO date range, calls clients.radarr.getCalendar(start, end), and returns the JSON response.
    case "radarr_get_calendar": {
      if (!clients.radarr) throw new Error("Radarr 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.radarr.getCalendar(start, end);
      return {
        content: [{ type: "text", text: JSON.stringify(calendar, null, 2) }],
      };
    }
  • The tool registration/schema for 'radarr_get_calendar' in the TOOLS array. Defines the tool name, description ('Get upcoming movie releases from Radarr'), and input schema with an optional 'days' parameter (default 30).
      name: "radarr_get_calendar",
      description: "Get upcoming movie releases from Radarr",
      inputSchema: {
        type: "object" as const,
        properties: {
          days: {
            type: "number",
            description: "Number of days to look ahead (default: 30)",
          },
        },
        required: [],
      },
    },
  • src/index.ts:437-449 (registration)
    The tool is registered in the TOOLS array at lines 436-449, conditional on clients.radarr being configured (line 380).
      name: "radarr_get_calendar",
      description: "Get upcoming movie releases from Radarr",
      inputSchema: {
        type: "object" as const,
        properties: {
          days: {
            type: "number",
            description: "Number of days to look ahead (default: 30)",
          },
        },
        required: [],
      },
    },
  • The getCalendar method on the base ArrClient class. Accepts optional start/end strings, appends them as query parameters, and makes a GET request to /calendar.
    /**
     * Get calendar items (upcoming releases)
     */
    async getCalendar(start?: string, end?: string): Promise<unknown[]> {
      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<unknown[]>(`/calendar${query}`);
    }
  • The RadarrClient class extends ArrClient. It inherits the getCalendar method (defined in ArrClient at lines 442-448) with no override, so the base implementation is used.
    export class RadarrClient extends ArrClient {
      constructor(config: ArrConfig) {
        super('radarr', config);
      }
    
      /**
       * Get all movies
       */
      async getMovies(): Promise<Movie[]> {
        return this['request']<Movie[]>('/movie');
      }
    
      /**
       * Get a specific movie
       */
      async getMovieById(id: number): Promise<Movie> {
        return this['request']<Movie>(`/movie/${id}`);
      }
    
      /**
       * Search for movies
       */
      async searchMovies(term: string): Promise<SearchResult[]> {
        return this['request']<SearchResult[]>(`/movie/lookup?term=${encodeURIComponent(term)}`);
      }
    
      /**
       * Add a movie
       */
      async addMovie(movie: Partial<Movie> & { tmdbId: number; rootFolderPath: string; qualityProfileId: number }): Promise<Movie> {
        return this['request']<Movie>('/movie', {
          method: 'POST',
          body: JSON.stringify({
            ...movie,
            monitored: movie.monitored ?? true,
            addOptions: {
              searchForMovie: true,
            },
          }),
        });
      }
    
      /**
       * Trigger a search for a movie
       */
      async searchMovie(movieId: number): Promise<{ id: number }> {
        return this['request']<{ id: number }>('/command', {
          method: 'POST',
          body: JSON.stringify({
            name: 'MoviesSearch',
            movieIds: [movieId],
          }),
        });
      }
    
      /**
       * Trigger a refresh for a specific movie
       */
      async refreshMovie(movieId: number): Promise<{ id: number }> {
        return this['request']<{ id: number }>('/command', {
          method: 'POST',
          body: JSON.stringify({
            name: 'RefreshMovie',
            movieIds: [movieId],
          }),
        });
      }
Behavior1/5

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

With no annotations, the description must disclose behavior like read-only nature, output format, or side effects. It only states the purpose without any behavioral details, leaving the agent without critical context.

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, front-loaded sentence with no unnecessary words. It is appropriately concise for the tool's simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the tool's simplicity, the description lacks context about return values, default behavior, and limitations. Without annotations or output schema, the description should provide more operational context.

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 already fully describes the only parameter ('days'), so the description adds no extra meaning. Baseline of 3 is appropriate given 100% schema coverage.

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 movie releases from Radarr'), differentiating it from other Radarr tools like radarr_get_movies. However, it could be more specific about the time range.

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 on when to use this tool versus alternatives such as radarr_get_movies or other calendar tools (e.g., sonarr_get_calendar). The context does not help the agent decide.

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