Skip to main content
Glama

trash_compare_profile

Read-only

Compare a Radarr or Sonarr quality profile with TRaSH Guides recommendations to identify missing custom formats, scoring differences, and quality setting changes.

Instructions

Compare your quality profile against TRaSH Guides recommendations. Shows missing custom formats, scoring differences, and quality settings. Requires the corresponding *arr service to be configured.

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": {
      "service": "<service>",
      "profileId": "<profileId>",
      "trashProfile": "<trashProfile>"
    },
    "name": "trash_compare_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYesWhich service
profileIdYesYour quality profile ID to compare
trashProfileYesTRaSH profile name to compare against

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.9.0
    • addedInput schema / properties / profileId / minimum
      Added value: +1
    • changedInput schema / properties / profileId / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A3.8/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 value by naming the prerequisite configuration and the categories of results returned, but says nothing about how the TRaSH profile is matched or what happens when no match is found.

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?

Three short sentences, front-loaded with the action and followed by outputs and the prerequisite. No redundant or filler wording.

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 read-only comparison tool with no output schema, the description covers purpose, result categories, and the configuration prerequisite. Only the behavior on unmatched or missing profiles is left unstated, a minor gap.

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?

Schema description coverage is 100%, with each of the three required parameters documented in the schema, including the service enum. The description adds no parameter-level detail beyond that, so the baseline of 3 applies.

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 and resource: 'Compare your quality profile against TRaSH Guides recommendations.' It also enumerates the comparison outputs (missing custom formats, scoring differences, quality settings), which distinguishes it from siblings like trash_compare_naming and trash_get_profile.

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 prerequisite 'Requires the corresponding *arr service to be configured' is useful context, but there is no explicit when-to-use guidance or routing to alternatives such as trash_get_profile for a plain profile fetch. Usage is only implied by the comparison framing.

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