Skip to main content
Glama

radarr_get_calendar

Read-only

Get upcoming movie releases from Radarr for a specified number of days ahead (default 30) to plan what to watch.

Instructions

Get upcoming movie releases from Radarr

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "radarr_get_calendar"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing further: it does not say whether results include unmonitored or already-downloaded movies, whether entries without confirmed release dates appear, or how the window is anchored (today vs. digital/physical dates).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is part of why behavioral and usage detail are thin.

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?

This is a simple read-only tool with one optional parameter and no output schema, so the burden is modest. Still, an agent would benefit from knowing the shape of a calendar entry and the date basis used, neither of which is stated.

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% and the single optional "days" parameter is fully documented in the schema, including its default of 30. The description adds no extra meaning about the parameter, so the baseline 3 applies.

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?

States a specific verb and resource ("Get upcoming movie releases") with the service named ("from Radarr"), which implicitly separates it from the lidarr/sonarr calendar siblings by media type. It does not explicitly name those alternatives, so it stops short of full sibling differentiation.

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?

There is no when-to-use or when-not-to-use guidance and no reference to alternatives such as radarr_get_movies for the full library or radarr_search_movie for targeted lookup. The word "upcoming" hints at a time-window view, but the agent must infer that this is the calendar/release-schedule tool.

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

Deploy Server

Other Tools