Skip to main content
Glama

radarr_get_health

Get health check warnings and issues from Radarr. Shows any problems detected by the movie management application.

Instructions

Get health check warnings and issues from Radarr (Movies). Shows any problems detected by the application.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:143-151 (registration)
    The tool 'radarr_get_health' is registered via the addConfigTools('radarr', 'Radarr (Movies)') call on line 202, which dynamically creates the tool definition at lines 143-151 with name `${serviceName}_get_health`.
    {
      name: `${serviceName}_get_health`,
      description: `Get health check warnings and issues from ${displayName}. Shows any problems detected by the application.`,
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • src/index.ts:201-203 (registration)
    The addConfigTools function is called for radarr here, triggering registration of radarr_get_health tool.
    if (clients.sonarr) addConfigTools('sonarr', 'Sonarr (TV)');
    if (clients.radarr) addConfigTools('radarr', 'Radarr (Movies)');
    if (clients.lidarr) addConfigTools('lidarr', 'Lidarr (Music)');
  • Handler for the 'radarr_get_health' tool case in the switch statement. Extracts service name from tool name, calls client.getHealth(), and returns formatted JSON with issue count, issues (source, type, message, wikiUrl), and overall status.
    // Health checks
    case "sonarr_get_health":
    case "radarr_get_health":
    case "lidarr_get_health": {
      const serviceName = name.split('_')[0] as keyof typeof clients;
      const client = clients[serviceName];
      if (!client) throw new Error(`${serviceName} not configured`);
      const health = await client.getHealth();
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            issueCount: health.length,
            issues: health.map(h => ({
              source: h.source,
              type: h.type,
              message: h.message,
              wikiUrl: h.wikiUrl,
            })),
            status: health.length === 0 ? 'healthy' : 'issues detected',
          }, null, 2),
        }],
      };
    }
  • The getHealth() method on the base ArrClient class which handles the actual API call to /health endpoint. Both SonarrClient and RadarrClient inherit this method.
    /**
     * Get health check issues
     */
    async getHealth(): Promise<HealthCheck[]> {
      return this.request<HealthCheck[]>('/health');
    }
  • The HealthCheck interface defining the shape of health check data returned from the API (source, type, message, wikiUrl).
    export interface HealthCheck {
      source: string;
      type: string;
      message: string;
      wikiUrl: string;
    }
Behavior4/5

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

With no annotations, the description carries the transparency burden. It clearly states 'Get' and 'Shows', indicating read-only behavior without side effects. This is adequate for a zero-parameter health check tool.

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?

The description is two concise sentences with no unnecessary information. It is well-structured and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with no parameters and no output schema, the description fully explains its purpose and output. No additional context is needed.

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?

No parameters exist, so baseline is 4. The description does not need to add parameter-level detail.

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?

The description clearly states the tool retrieves health check warnings and issues from Radarr, specifying the application and its purpose. The mention of 'Radarr (Movies)' differentiates it from sibling health tools for Lidarr and Sonarr.

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

Usage Guidelines4/5

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

The description implies usage for checking health status of Radarr, and the name and context clearly indicate it's for Radarr only. However, it does not explicitly describe when to use this tool versus alternatives, but the context is sufficient.

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