Skip to main content
Glama

sonarr_review_setup

Read-only

Review Sonarr TV configuration settings—quality profiles, download clients, naming, storage, indexers, and health warnings—to analyze your setup and identify improvements.

Instructions

Get comprehensive configuration review for Sonarr (TV). Returns all settings for analysis: quality profiles, download clients, naming, storage, indexers, health warnings, and more. Use this to analyze the setup and suggest improvements.

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": "sonarr_review_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 the useful fact that this is a multi-domain aggregate pull rather than a targeted read. It does not disclose anything about response size, latency from fanning out to many endpoints, or whether partial failures are reported.

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?

Three short sentences, front-loaded with the verb and resource, then the contents, then the intended use. 'and more' is the only filler phrase, and it hedges rather than misleads.

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 no parameters, no nested schema, and no output schema, the description's main burden is telling the agent what comes back — and the enumeration of settings domains does that adequately. It stops short of describing the response shape (key names, nesting, health-warning structure), which matters somewhat for an aggregate audit tool.

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?

The tool takes zero parameters, which is the baseline-4 case per the rubric. There is no argument surface for the description to explain, and it correctly frames the tool as scope-free ('all settings').

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 comprehensive configuration review for Sonarr (TV)') and enumerates the domains covered (quality profiles, download clients, naming, storage, indexers, health). The enumeration signals that this is an aggregate audit rather than a single-resource getter, though it never names the sibling getters it supersedes.

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?

'Use this to analyze the setup and suggest improvements' gives an intent-level cue for when to call it, but there is no explicit contrast with alternatives such as sonarr_get_quality_profiles or sonarr_get_health, nor any when-not guidance (e.g., skip when you only need one section).

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