Skip to main content
Glama

trash_get_profile

Read-only

Retrieve a specific TRaSH Guides quality profile for Radarr or Sonarr, including custom format scores, quality settings, and implementation details.

Instructions

Get a specific TRaSH Guides quality profile with all custom format scores, quality settings, and implementation details

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>",
      "profile": "<profile>"
    },
    "name": "trash_get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYesProfile name (e.g., 'remux-web-1080p', 'uhd-bluray-web', 'hd-bluray-web')
serviceYesWhich service

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 detail about the returned contents (custom format scores, quality settings, implementation details), but says nothing about where the data comes from, whether it is cached, or what happens when the profile name is not found.

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 no wasted framing, which is well matched to a simple two-parameter read tool. The trailing phrase "implementation details" is slightly vague but does not obscure the core purpose.

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 two-parameter lookup with fully covered schema and no output schema, the description does the needed work by listing the returned fields. It falls short only on failure behavior (missing profile) and the remote TRaSH Guides source, which would matter for error handling.

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%, so both the profile name and the radarr/sonarr enum are already documented with examples. The description adds no additional parameter semantics beyond confirming that a specific profile is fetched; 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 pairs a specific verb ("Get") with a specific resource ("a specific TRaSH Guides quality profile") and enumerates what the payload contains. The word "specific" implicitly separates it from list/compare siblings, though no sibling is named explicitly.

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: an agent can infer this is the lookup to use once a profile name is known, versus trash_list_profiles or trash_compare_profile. There is no explicit statement of when to use it, when not to, or prerequisites such as needing a valid profile name or service.

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