Skip to main content
Glama

trash_compare_naming

Read-only

Compares your Radarr or Sonarr naming configuration with TRaSH Guides recommendations to identify mismatches and guide corrections. Requires the target service to be configured.

Instructions

Compare your naming configuration against TRaSH Guides recommendations. 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>",
      "mediaServer": "<mediaServer>"
    },
    "name": "trash_compare_naming"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYesWhich service
mediaServerYesWhich media server you use

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 safety is covered. The description adds a real operational constraint (the *arr service must be configured) that the annotations don't convey. It does not explain what the comparison produces — a diff, a pass/fail, a list of mismatches — leaving the agent to guess at the result shape.

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 with zero filler; the action is front-loaded and the prerequisite follows. Nothing could be removed without losing information.

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 two-parameter read-only comparison with full schema coverage and no output schema, the definition covers purpose and the key precondition. The only gap is that the nature of the returned comparison is never characterized, which matters slightly for deciding whether one call answers the question.

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% and both parameters carry enums, so the schema already defines acceptable values. The phrase 'the corresponding *arr service' loosely ties the service parameter to the configured instance, but adds no real meaning beyond the enum. Baseline 3 applies.

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 states a specific verb and resource: compare the user's naming configuration against TRaSH Guides recommendations. This is clearly distinct from a plain fetch of guide values (e.g. trash_get_naming) and from trash_compare_profile, which targets profiles rather than naming. It stops short of naming those siblings explicitly, so it lands 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?

It gives one useful precondition — the corresponding *arr service must be configured — which tells the agent when the call will fail. It does not say when an agent should compare versus simply retrieve the reference naming, nor does it mention alternatives, so usage is only implied.

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