Loading ToolBench
Radarr MCP server has well-structured tool definitions with complete schemas and clear descriptions. All 8 tools have proper input schemas with type definitions and parameter descriptions. Tool names follow verb_noun convention (search, get, add, delete). Descriptions are substantive (100-200 chars typical), explaining WHAT the tool does and WHEN to use it. However, output schemas are not documented, LLMs cannot see what fields to expect from responses. Error handling is minimal; no recovery guidance or actionable error messages visible. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications. Parameter descriptions could be more prescriptive about formats and constraints. Missing documentation of response structures limits downstream tool chaining.
Add a new movie to your library. You need the tmdbId from radarr_search_movies. Optionally specify root folder path, quality profile, and minimum availability.
Delete a movie from Radarr. Optionally delete files from disk. WARNING: This cannot be undone!
Get all movies in your Radarr library. Returns complete list with metadata, file status, and ratings.
Get detailed information about a specific movie by its Radarr ID. Includes file info, ratings, and collection data.
Get movie information by TMDB ID. Useful when you know the TMDB ID but not the Radarr ID.
Get current download queue. Shows active downloads, their progress, status, and any errors.
Output schemas not documented. LLMs cannot see what fields responses contain (e.g., what does radarr_search_movies return? Is it an array of movies with tmdbId, title, year?). This breaks downstream tool chaining and forces agents to guess field names.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk classifications. radarr_delete_movie is DESTRUCTIVE but lacks annotation. radarr_add_movie is WRITE but unmarked. Agents cannot distinguish safe reads from dangerous mutations without annotations.
Error handling is absent from visible code. No recovery guidance, no actionable error messages, no error classification (retryable vs fatal). If radarr_add_movie fails due to invalid tmdbId, the agent has no guidance on what to do next.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | B | 73 | 2026-07-28+ | v2 |
Search for a specific movie to download. This sends the movie to your download client. Use the movieId from your library.
Search for movies by title on TMDB. Returns potential matches with metadata. Use this to find the tmdbId needed to add a movie.
Parameter descriptions lack prescriptive constraints. 'rootFolderPath' has no format guidance (absolute path? relative? examples?). 'minimumAvailability' enum is documented but no explanation of when to use each value. 'tags' array has no min/max length or validation rules.
radarr_delete_movie description lacks confirmation/dry-run guidance. Destructive operations should warn agents and offer a confirmation step. Current description only says 'WARNING: This cannot be undone!' but no mitigation pattern.