Skip to main content
Glama

radarr_get_command

Read-only

Retrieve Radarr command status by ID to check manual-import completion or failure, then verify the actual movie files after the command finishes.

Instructions

Read Radarr command status by ID, including manual-import completion or failure. Verify actual movie files after completion.

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": {
      "commandId": "<commandId>"
    },
    "name": "radarr_get_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.4

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 is covered. The description adds real behavioral value by saying the response reports completion or failure, notably for manual imports. It omits what happens for an unknown/expired command ID and does not describe the shape of the status payload.

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 core action and followed by the natural next step. No filler or restatement of the name; only a slightly terse second sentence that assumes the reader knows why file verification follows.

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 one-parameter read tool with no output schema, the description covers the essential outcome (completion/failure) but leaves return shape, unknown-ID behavior, and ID provenance unspecified. Adequate, but not fully self-sufficient for an agent unfamiliar with Radarr commands.

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 0% for the single commandId parameter, so the description must carry the burden and largely does not — it only restates 'by ID.' It never says where a commandId comes from (which sibling returns one), though the integer ID semantics are simple enough that little else is needed.

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?

States a concrete verb and resource: reading Radarr command status by ID, with the additional scope of manual-import completion or failure. An agent can distinguish it from siblings such as radarr_manual_import (which triggers work) and radarr_get_movie_files (which reads files). It stops short of explicitly naming those siblings.

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?

'Verify actual movie files after completion' implies the workflow: poll/read a command after triggering it, then confirm with a file query. However, no alternative is named, no guidance is given on when not to use it (e.g., when the command ID is unknown), and polling behavior is left implicit.

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