Skip to main content
Glama

readarr_get_health

Retrieve health check warnings and issues from Readarr to identify problems detected in your book management system.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler for the 'readarr_get_health' tool. Parses the tool name to get the service, retrieves the ReadarrClient instance, calls getHealth(), formats the health issues into JSON, and returns as text content.
    case "sonarr_get_health":
    case "radarr_get_health":
    case "lidarr_get_health":
    case "readarr_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),
        }],
      };
    }
  • Tool schema definition for readarr_get_health (and other *_get_health tools). Defines name, description, and empty input schema (no parameters required).
      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:175-179 (registration)
    Registration of configuration tools including readarr_get_health. Conditionally adds the tool to the TOOLS array if Readarr client is configured.
    if (clients.sonarr) addConfigTools('sonarr', 'Sonarr (TV)');
    if (clients.radarr) addConfigTools('radarr', 'Radarr (Movies)');
    if (clients.lidarr) addConfigTools('lidarr', 'Lidarr (Music)');
    if (clients.readarr) addConfigTools('readarr', 'Readarr (Books)');
  • Core getHealth() method in ArrClient (inherited by ReadarrClient). Makes API request to /health endpoint to fetch health checks.
     * Get health check issues
     */
    async getHealth(): Promise<HealthCheck[]> {
      return this.request<HealthCheck[]>('/health');
    }
  • Type definition for HealthCheck interface used by getHealth() method.
    export interface HealthCheck {
      source: string;
      type: string;
      message: string;
      wikiUrl: string;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the tool retrieves health check data but doesn't describe critical behaviors like whether it's read-only (implied by 'Get'), authentication requirements, rate limits, error handling, or response format. For a tool with zero annotation coverage, this leaves significant gaps in understanding its operational characteristics.

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 highly concise and well-structured. It uses two clear sentences: the first states the core purpose, and the second adds context about what it shows. There is no wasted language, and information is front-loaded effectively, making it easy to understand at a glance.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has gaps. It explains what the tool does but lacks details on behavioral aspects (e.g., response format, error conditions) that would be helpful for an AI agent. For a read-only health-check tool, it meets minimum viability but could be more complete by addressing missing behavioral context.

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 has 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, as there are none to explain. A baseline score of 4 is appropriate for tools with no parameters, as the description's focus can be entirely on purpose and behavior without parameter overhead.

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 clearly states the tool's purpose: 'Get health check warnings and issues from Readarr (Books).' It specifies the verb ('Get'), resource ('health check warnings and issues'), and domain ('Readarr (Books)'). However, it doesn't explicitly differentiate from sibling tools like 'lidarr_get_health' or 'radarr_get_health', which perform similar functions in different media domains.

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?

The description provides minimal usage guidance. It states 'Shows any problems detected by the application,' which implies it should be used when checking for system issues, but it doesn't specify when to use this tool versus alternatives (e.g., other health-check tools for different media types or general status tools). No explicit when/when-not instructions or prerequisites are provided.

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