arr-mcp

Overview Schema Source Related Servers Discussions Admin

Upcoming releases

get_calendar

Read-only

Retrieve films, episodes, and albums due in a date window across Radarr, Sonarr, Whisparr, and Lidarr, sorted by date and showing whether each item already has a file.

Instructions

Films, episodes and albums due in a date window, merged from Radarr, Sonarr, Whisparr and Lidarr and sorted by date. Covers both upcoming releases and recently aired items, with whether each already has a file (an album only once every track is on disk).

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum items to return. Defaults to 50, hard maximum 500.
`detail`	No	How much per-item detail to return. Defaults to standard.	standard
`offset`	No	Items to skip: page two of 50 is `offset: 50`. Pair it with `sort`, or items can move between pages.
`days_back`	No	How many days of already-released items to include. Defaults to 7.
`days_ahead`	No	How many days ahead to include. Defaults to 14.

Output Schema

Name	Required	Description	Default
`items`	Yes
`total`	Yes
`counts`	No
`offset`	Yes
`degraded`	Yes
`returned`	Yes
`truncated`	Yes
`missingFiles`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv1.74.0Nov 9, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / offset / description

Previous value: -"How many items to skip before the window `limit` returns — page two of 50 is `offset: 50`. `total` always counts the whole list, so `offset + returned < total` is how you know there is another page. Pair it with `sort` for a stable walk: without one the order is whatever the services returned, and an item can move between pages."New value: +"Items to skip: page two of 50 is `offset: 50`. Pair it with `sort`, or items can move between pages."

removedInput schema / properties / offset / maximum
```
Removed value: -9007199254740991
```

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / properties / counts / description

Removed value: -"How many results each service contributed."

removedOutput schema / properties / degraded / description

Removed value: -"Services that could not be reached. Their contribution is missing from `items`, so a short list may be an outage rather than an answer."

removedOutput schema / properties / items / description

Removed value: -"The window of results. What an item carries depends on the tool and on `detail`."

removedOutput schema / properties / missingFiles / description

Removed value: -"How many of the returned items have no file yet, an album until every track is on disk. Counted before the detail projection, so it is right at every detail level."

removedOutput schema / properties / offset / description

Removed value: -"How many were skipped. `offset + returned < total` means there is another page."

removedOutput schema / properties / offset / maximum
```
Removed value: -9007199254740991
```
removedOutput schema / properties / offset / minimum
```
Removed value: --9007199254740991
```
removedOutput schema / properties / returned / description
```
Removed value: -"How many are in `items`."
```
removedOutput schema / properties / returned / maximum
```
Removed value: -9007199254740991
```
removedOutput schema / properties / returned / minimum
```
Removed value: --9007199254740991
```

removedOutput schema / properties / total / description

Removed value: -"How many matched in total — the whole list, never the window. Compare against `returned` before reporting a count to anyone."

removedOutput schema / properties / total / maximum
```
Removed value: -9007199254740991
```
removedOutput schema / properties / total / minimum
```
Removed value: --9007199254740991
```

removedOutput schema / properties / truncated / description

Removed value: -"True when this is not the whole list — including on the last page of a paged walk, where the rest is behind you rather than ahead."

First observedv0.1.0Nov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds genuinely useful behavior: results are merged across four services and sorted by date, and each item carries a has-file indicator with the specific rule that an album only counts once every track is on disk. That file-completeness nuance is non-obvious and would be hard to infer from the schema. It does not discuss pagination stability beyond what the schema already says.

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?

Two sentences, front-loaded with the resource and sources, then the temporal scope and file-status rule. Every clause carries information; nothing is redundant padding.

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

Completeness4/5

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

With an output schema present, return-shape explanation is unnecessary, and all five parameters are fully documented in the schema. What remains thin is the relationship to overlapping siblings (get_releases, get_wanted) and any hint about how the merged feed orders items sharing a date.

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?

Schema description coverage is 100%, so the baseline is 3. The description's 'date window' framing loosely maps to days_back/days_ahead and the file-presence note hints at output content, but it adds no format, boundary, or interaction guidance beyond what the schema already documents.

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 names a concrete resource (films, episodes, albums due in a date window), the four source services it merges, and the sort order, so an agent knows exactly what comes back. It stops short of distinguishing itself from siblings like get_releases or get_wanted, which sound adjacent and could be confused with a date-window release feed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the phrase 'date window' plus the note that it covers both upcoming and recently aired items suggests when this is the right call. There is no explicit when-to-use, when-not-to-use, or named alternative such as get_releases for a different view of the same data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.