Skip to main content
Glama

trash_list_custom_formats

Read-only

Lists available TRaSH Guides custom formats for Radarr or Sonarr, with optional category filters to narrow results by HDR, audio, resolution, source, streaming, anime, unwanted, release, or language.

Instructions

List available TRaSH Guides custom formats. Can filter by category: hdr, audio, resolution, source, streaming, anime, unwanted, release, language

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

Input Schema

NameRequiredDescriptionDefault
serviceYesWhich service
categoryNoOptional filter by category

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?

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile and network-touching nature come from structured data. The description adds little behavioral context, such as whether an unfiltered call returns the entire catalog or how large/unstable the list is. That leaves some behavioral gaps.

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?

Two sentences, front-loaded with the core purpose before the filter details. The trailing inline list of categories is slightly dense but not wasteful.

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?

This is a simple read-only list tool with full schema coverage, no output schema, and annotations covering safety. The description plus schema is enough to invoke it correctly. The only minor gap is behavior when no category is supplied.

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?

Schema coverage is 100%, so the baseline would be 3. However, it adds meaningful semantics beyond the schema: the schema describes category only as 'Optional filter by category', while the description enumerates the valid values (hdr, audio, resolution, etc.), which is real information not present in the schema.

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 opens with a specific verb and resource: 'List available TRaSH Guides custom formats.' That distinguishes it from siblings like trash_get_profile or trash_list_profiles, though it never names a sibling explicitly. The second sentence clarifies the filtering scope.

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: the agent learns it can filter by category, but there is no guidance on when to call this versus trash_list_profiles or the compare tools. No exclusions, prerequisites, or fallback conditions are stated.

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