Skip to main content
Glama

readarr_get_calendar

Retrieve upcoming book release dates from Readarr to plan your reading schedule and manage library updates.

Instructions

Get upcoming book releases from Readarr

Input Schema

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

Implementation Reference

  • MCP tool handler for 'readarr_get_calendar'. Computes date range from input 'days' (default 30), calls ReadarrClient.getCalendar(start, end), and returns count and list of upcoming books with id, title, authorId, releaseDate, monitored status.
    case "readarr_get_calendar": {
      if (!clients.readarr) throw new Error("Readarr 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.readarr.getCalendar(start, end);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: calendar.length,
            books: calendar.map(b => ({
              id: b.id,
              title: b.title,
              authorId: b.authorId,
              releaseDate: b.releaseDate,
              monitored: b.monitored,
            })),
          }, null, 2),
        }],
      };
    }
  • src/index.ts:440-532 (registration)
    Conditional registration of Readarr tools in TOOLS array, including the schema definition for 'readarr_get_calendar' tool with optional 'days' parameter.
    if (clients.readarr) {
      TOOLS.push(
        {
          name: "readarr_get_authors",
          description: "Get all authors in Readarr library",
          inputSchema: {
            type: "object" as const,
            properties: {},
            required: [],
          },
        },
        {
          name: "readarr_search",
          description: "Search for authors to add to Readarr",
          inputSchema: {
            type: "object" as const,
            properties: {
              term: {
                type: "string",
                description: "Search term (author name)",
              },
            },
            required: ["term"],
          },
        },
        {
          name: "readarr_get_queue",
          description: "Get Readarr download queue",
          inputSchema: {
            type: "object" as const,
            properties: {},
            required: [],
          },
        },
        {
          name: "readarr_get_books",
          description: "Get books for an author in Readarr. Shows which books are available and which are missing.",
          inputSchema: {
            type: "object" as const,
            properties: {
              authorId: {
                type: "number",
                description: "Author ID to get books for",
              },
            },
            required: ["authorId"],
          },
        },
        {
          name: "readarr_search_book",
          description: "Trigger a search for a specific book to download",
          inputSchema: {
            type: "object" as const,
            properties: {
              bookIds: {
                type: "array",
                items: { type: "number" },
                description: "Book ID(s) to search for",
              },
            },
            required: ["bookIds"],
          },
        },
        {
          name: "readarr_search_missing",
          description: "Trigger a search for all missing books for an author",
          inputSchema: {
            type: "object" as const,
            properties: {
              authorId: {
                type: "number",
                description: "Author ID to search missing books for",
              },
            },
            required: ["authorId"],
          },
        },
        {
          name: "readarr_get_calendar",
          description: "Get upcoming book releases from Readarr",
          inputSchema: {
            type: "object" as const,
            properties: {
              days: {
                type: "number",
                description: "Number of days to look ahead (default: 30)",
              },
            },
            required: [],
          },
        }
      );
    }
  • Tool schema definition: name, description, and inputSchema with optional 'days' number parameter.
      name: "readarr_get_calendar",
      description: "Get upcoming book releases from Readarr",
      inputSchema: {
        type: "object" as const,
        properties: {
          days: {
            type: "number",
            description: "Number of days to look ahead (default: 30)",
          },
        },
        required: [],
      },
    }
  • ReadarrClient.getCalendar method: constructs /calendar?start=...&end=... API endpoint and calls base request method to fetch upcoming Book[] releases.
    async getCalendar(start?: string, end?: string): Promise<Book[]> {
      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']<Book[]>(`/calendar${query}`);
    }
  • Base ArrClient.getCalendar: generic implementation for /calendar endpoint used by all *arr clients (overridden in ReadarrClient for Book[] typing).
    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}`);
    }
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 offers minimal behavioral insight. It states what the tool does but doesn't cover critical aspects like whether this is a read-only operation, potential rate limits, authentication requirements, or the format of returned data (e.g., list of books with dates).

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 tool with one optional parameter and no output schema, the description is minimally adequate but lacks depth. It doesn't explain what 'upcoming' entails (e.g., release dates within the specified days), the structure of returned data, or how it differs from similar calendar tools, leaving gaps 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 input schema has 100% description coverage (the 'days' parameter is fully documented), so the baseline is 3. The description doesn't add any parameter-specific information beyond what the schema provides, such as clarifying what 'upcoming' means relative to the 'days' 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 book releases from Readarr'), making the purpose immediately understandable. However, it doesn't differentiate from sibling calendar tools like 'lidarr_get_calendar', 'radarr_get_calendar', and 'sonarr_get_calendar' beyond specifying 'Readarr' as the source.

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. While the description specifies 'Readarr' for book releases, it doesn't mention when to prefer this over other calendar tools (e.g., for movies vs. books) or other Readarr tools like 'readarr_get_books' for existing books.

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