Skip to main content
Glama

sonarr_get_quality_profiles

Read-only

Fetch Sonarr TV quality profiles to inspect allowed qualities, upgrade rules, and custom format scores for selecting or troubleshooting profile settings.

Instructions

Get detailed quality profiles from Sonarr (TV). Shows allowed qualities, upgrade settings, and custom format scores.

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_get_quality_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 bar is lower. The description adds genuine value by listing the data each profile carries (allowed qualities, upgrade cutoffs, custom format scores), which tells the agent what to expect in the response. It does not state that the full unfiltered list is returned or roughly how many profiles to expect, leaving some behavioral detail uncovered.

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?

Two sentences with the identity of the resource front-loaded and the payload details second. Nothing is repeated from the name and no sentence is wasted.

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?

For a parameterless read tool with no output schema and full annotation coverage, the definition supplies enough for correct selection and invocation. The only gap is that the return shape and profile count are not described, which is minor given the low complexity.

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 has zero parameters, so there is no schema semantics for the description to supplement; the baseline for a parameterless tool is 4. The description correctly does not invent parameter-like qualifiers, confirming the agent can call it directly.

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?

The description gives a specific verb and resource ('Get detailed quality profiles from Sonarr') and scopes the resource to TV, which separates it from the Radarr/Lidarr equivalents. It also enumerates the profile contents (allowed qualities, upgrade settings, custom format scores), so the agent knows exactly what a 'quality profile' means here. It stops short of naming the sibling tools explicitly, which keeps it at 4 rather than 5.

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?

The domain tag '(TV)' implies when this tool applies and when the movie or music variants do, but the description gives no explicit when-to-use or when-not-to-use statement. For a simple parameterless retrieval, no alternatives need to be weighed, so the implied guidance is adequate but not instructive.

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