Skip to main content
Glama

sonarr_get_root_folders

Read-only

Retrieve Sonarr root folders and storage details, including paths, free space, and unmapped folders, to verify where TV series are stored and whether disk space is available.

Instructions

Get root folders and storage info from Sonarr (TV). Shows paths, free space, and unmapped folders.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 content beyond that by enumerating the returned data (paths, free space, unmapped folders), which matters because there is no output schema; only the meaning of 'unmapped folders' and units of free space are left unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler: the first states the action and target, the second enumerates the output. Information is front-loaded and appropriately sized for a zero-argument read tool.

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 parameterless, read-only listing tool without an output schema, the description covers what is needed: what it returns and where it comes from. Minor gaps remain around what an 'unmapped folder' signifies and whether free-space values are bytes or GB, but nothing blocks correct invocation.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline of 4 applies. Nothing in the description misrepresents or over-complicates the empty input 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?

Uses a specific verb ('Get') with a concrete resource ('root folders and storage info') and scopes it to Sonarr (TV), which separates it from the lidarr/radarr root-folder siblings. It also names the returned fields (paths, free space, unmapped folders), so the agent knows exactly what data this yields.

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: checking storage capacity and discovering folder paths (e.g. before adding a series). There is no explicit when-to-use, no exclusions, and no pointer to alternatives such as sonarr_get_health or sonarr_review_setup, which could plausibly overlap on storage diagnostics.

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