Skip to main content
Glama

radarr_get_root_folders

Retrieve root folder paths, free space, and unmapped folders from Radarr for movie storage management.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:152-160 (registration)
    The tool 'radarr_get_root_folders' is registered in the TOOLS array via the addConfigTools() function. It's created dynamically with the name `${serviceName}_get_root_folders` where serviceName is 'radarr' (line 202). The description states it returns root folders and storage info with paths, free space, and unmapped folders.
    {
      name: `${serviceName}_get_root_folders`,
      description: `Get root folders and storage info from ${displayName}. Shows paths, free space, and unmapped folders.`,
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • The input schema for 'radarr_get_root_folders' is an empty object with no required properties (type: object, properties: {}, required: []), meaning it takes no arguments.
    inputSchema: {
      type: "object" as const,
      properties: {},
      required: [],
    },
  • The handler for 'radarr_get_root_folders' is in the CallToolRequestSchema switch statement at case 'radarr_get_root_folders' (line 1246). It delegates to the service name extracted from the tool name, calls the client's getRootFoldersDetailed() method, and returns formatted JSON with count, folders (id, path, accessible, freeSpace formatted as human-readable, freeSpaceBytes, unmappedFolders count).
    case "radarr_get_root_folders":
    case "lidarr_get_root_folders": {
      const serviceName = name.split('_')[0] as keyof typeof clients;
      const client = clients[serviceName];
      if (!client) throw new Error(`${serviceName} not configured`);
      const folders = await client.getRootFoldersDetailed();
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: folders.length,
            folders: folders.map(f => ({
              id: f.id,
              path: f.path,
              accessible: f.accessible,
              freeSpace: formatBytes(f.freeSpace),
              freeSpaceBytes: f.freeSpace,
              unmappedFolders: f.unmappedFolders?.length || 0,
            })),
          }, null, 2),
        }],
      };
    }
  • The getRootFoldersDetailed() method on ArrClient is the underlying API call. It makes a GET request to '/rootfolder' and returns an array of RootFolder objects (id, path, accessible, freeSpace, unmappedFolders).
     */
    async getRootFoldersDetailed(): Promise<RootFolder[]> {
      return this.request<RootFolder[]>('/rootfolder');
    }
  • The RootFolder interface defines the shape of data returned from the API: id, path, accessible, freeSpace, and optional unmappedFolders array.
    export interface RootFolder {
      id: number;
      path: string;
      accessible: boolean;
      freeSpace: number;
      unmappedFolders?: Array<{ name: string; path: string }>;
    }
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It discloses that it shows paths, free space, and unmapped folders, indicating a read operation. However, it does not mention any side effects, permissions, or rate limits, which would be beneficial.

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?

Description is a single, well-structured sentence that captures the tool's purpose and output. Every word adds value, no fluff.

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?

Given no parameters and no output schema, the description effectively communicates what the tool returns: paths, free space, and unmapped folders. It is complete enough for a simple listing tool, though it could mention if any additional info is included.

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?

No parameters exist, and schema coverage is 100%. The description adds no parameter information because none is needed. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it gets root folders and storage info, specifying it is for Radarr Movies. This distinguishes it from sibling tools like sonarr_get_root_folders or lidarr_get_root_folders. Verb 'Get' and resource 'root folders' are specific.

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?

No explicit guidance on when to use this tool versus alternatives. However, the mention of 'Movies' implies it is for Radarr, differentiating it from similar tools for other services. Usage is straightforward for a simple getter.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aplaceforallmystuff/mcp-arr'

If you have feedback or need assistance with the MCP directory API, please join our Discord server