Skip to main content
Glama

trash_get_naming

Read-only

Retrieve TRaSH Guides recommended naming conventions for Radarr or Sonarr based on your media server (Plex, Emby, Jellyfin, or standard).

Instructions

Get TRaSH Guides recommended naming conventions for your media server (Plex, Emby, Jellyfin, or standard)

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

Input Schema

NameRequiredDescriptionDefault
serviceYesWhich service
mediaServerYesWhich media server you use

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 and the external-source nature are covered structurally. The description adds that the data originates from TRaSH Guides and that output is keyed by media server, but says nothing about what the returned conventions look like or whether they are static references versus live queries.

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?

A single front-loaded sentence with the resource named first and the qualifier trailing; no filler or redundant sentences. The parenthetical enumeration is useful but slightly duplicates the enum already in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-enum read-only lookup this is largely adequate, but with no output schema the description should hint at what is returned (naming format patterns for folders/files) and how service and media server combine. That omission leaves the agent guessing about the response shape.

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 coverage is 100% with both parameters enum-constrained and described, so the schema already carries the meaning. The description restates the mediaServer options ('Plex, Emby, Jellyfin, or standard') and leaves the service enum to the schema, adding little beyond the structured data — the baseline of 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: retrieving TRaSH Guides recommended naming conventions, and narrows scope to media servers (Plex, Emby, Jellyfin, standard). It does not explicitly distinguish itself from the sibling trash_compare_naming, which appears to compare rather than fetch, so an agent must infer the split.

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?

Usage is only implied by the phrase 'for your media server' — there is no statement of when to prefer this over trash_compare_naming or the per-service radarr_get_naming/sonarr_get_naming tools. No prerequisites or exclusions are given, so the agent must reason about the alternative on its own.

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