Skip to main content
Glama
Sign In
Sonarr MCP Server

Sonarr MCP Server

by micky-devs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

interactive_search

Find downloadable releases for TV series episodes by specifying series ID, with optional season and episode filters.

Instructions

Search for available releases for a TV series episode

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "series_id": "<series_id>"
    },
    "name": "interactive_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
series_idYesSonarr series ID (use the ID from list_series output)
season_numberNoSeason number (optional, searches all seasons if not provided)
episode_numberNoEpisode number (optional, searches all episodes if not provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It only says 'search for available releases' without explaining side effects, return format, or interactive nature. Minimal disclosure.

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?

Single sentence, no wasted words, front-loaded with the key action. Could benefit from slight expansion on behavior without being verbose.

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

Completeness2/5

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

No output schema exists, so the description should explain return values or effect. It does not. With 3 parameters and no output schema, the description is insufficient for full understanding.

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?

Input schema has 100% coverage with clear parameter descriptions. The overall description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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?

Description clearly states it searches for available releases for a TV series episode. Verb+resource is specific and distinguishes from siblings like search_series (series search) and download_release.

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 from the description, but there is no explicit guidance on when to use this tool versus alternatives like search_series. No mention of prerequisites or context.

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