arr-doctor

search_missing

Trigger searches for every monitored missing Sonarr episode and/or Radarr movie; shows a count first and requires confirmation before bulk indexer hits.

Instructions

Trigger a search for every monitored missing episode (Sonarr) and/or movie (Radarr). Sonarr/Radarr normally find new releases through RSS on their own; mass searches hit every indexer once per item and can exceed indexer limits. Over a few items it first returns how many would be searched and needs confirm=true. Prefer narrower searches.

Examples: "Search everything that's missing", "Search all missing episodes of The Capture"

Input Schema

TableJSON Schema

Name	Required	Description
`series`	No	Limit the Sonarr search to one series
`confirm`	No	Required when many items would be searched (shows the count first)
`service`	No	'sonarr' or 'radarr'; omit to query both

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: mass searches hit every indexer once per item and can exceed indexer limits, and over a few items it returns a count first and requires confirm=true. The annotations only give the generic safety profile; the description supplies the actual rate-limit and two-step confirmation behavior.

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?

Front-loads the core action, follows with the important rate-limit/confirmation caveat, closes with the routing hint and concrete examples. No sentence is wasted.

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

Completeness5/5

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

Given an output schema exists, return values needn't be described. The description covers intent, risk, confirmation gating, and alternatives, so an agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning to confirm by describing the count-preview gating behavior that the schema only hints at. It does not elaborate on series/service beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (trigger a search) and resource (every monitored missing episode/movie across Sonarr/Radarr). It clearly scopes itself apart from list-style siblings like get_missing and the narrower search_episodes/search_season tools.

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

Usage Guidelines4/5

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

Explains when this mass-search is appropriate versus relying on normal RSS, and explicitly says 'Prefer narrower searches.' It stops short of naming the specific narrower siblings (search_episodes, search_season), leaving the agent to infer the exact alternative.

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