Skip to main content
Glama

lidarr_get_quality_profiles

Read-only

Fetch Lidarr music quality profiles, including allowed qualities, upgrade settings, and custom format scores, to review or select a profile.

Instructions

Get detailed quality profiles from Lidarr (Music). 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": "lidarr_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 safety profile is covered. The description adds useful context about what the payload contains (allowed qualities, upgrade settings, custom format scores), which matters because there is no output schema. It says nothing about latency, remote connectivity, or whether profiles are read live from the Lidarr instance.

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 short sentences, front-loaded with the verb and resource, then the returned content. No filler or redundant restatement of the name.

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 zero-parameter read with no output schema, the description supplies enough about the response contents to decide whether calling it is worthwhile. It could go slightly further, for example noting that returned profile IDs are used by other Lidarr calls, but nothing essential is missing.

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, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not invent or misdescribe any inputs.

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 detailed quality profiles') and scopes it to Lidarr (Music), which separates it from the radarr/sonarr quality-profile siblings. It stops short of explicitly naming those counterparts, but the service qualifier makes the target unambiguous.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of the adjacent lidarr_get_metadata_profiles tool. The second sentence ('Shows allowed qualities, upgrade settings, and custom format scores') implies the situations where the tool is appropriate, which is enough for implied usage but nothing more.

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