Skip to main content
Glama

sonarr_get_queue

Read-only

Retrieve Sonarr download queue entries with limit and offset pagination to review active and queued downloads.

Instructions

Get Sonarr download queue. Supports pagination with limit and offset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sonarr_get_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of queue items to return (default: 25, max: 100)
offsetNoNumber of queue items to skip before returning results (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.9.0
    • addedInput schema / properties / limit / minimum
      Added value: +0
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
  2. Changed2 schema fields changedv1.6.3
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Maximum number of queue items to return (default: 25, max: 100)",
      +  "type": "number"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Number of queue items to skip before returning results (default: 0)",
      +  "type": "number"
      +}
  3. First observed

TDQS

B3.2/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 only that pagination is supported, which is already visible in the schema, and says nothing about what a queue item contains, ordering, or whether in-progress downloads are included.

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 short sentences, front-loaded with the resource and followed by the only behavioral note. Nothing is wasted, though the brevity borders on under-specification rather than efficient density.

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 read-only, zero-required-parameter list tool with full schema coverage, this is minimally sufficient to call correctly. The absence of an output schema means the description could have said something about the shape of returned queue items, and that gap is left open.

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 the schema already documents defaults (25) and the max (100) for limit, plus offset semantics. The description's mention of "limit and offset" adds no meaning beyond those field descriptions, so the 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 names a specific verb and resource ("Get Sonarr download queue"), so an agent knows exactly which collection is fetched. It does not explicitly distinguish itself from the similarly named radarr_get_queue / lidarr_get_queue siblings, relying on the tool name and Sonarr prefix for that separation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says whether to call this before deleting a queue item, before grabbing releases, or as a health check. No alternatives or exclusions are named, so the agent must infer the context entirely from the tool name.

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