Skip to main content
Glama

lidarr_get_health

Retrieve health check warnings and issues from Lidarr to identify any problems detected by the application.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for lidarr_get_health (along with sonarr_get_health and radarr_get_health). It extracts the service name from the tool name, calls client.getHealth(), and returns the health check results as JSON.
    // 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 HealthCheck interface defining the shape of health check data returned from the API.
    export interface HealthCheck {
      source: string;
      type: string;
      message: string;
      wikiUrl: string;
    }
  • The getHealth() method on ArrClient that makes the GET /api/v3/health (or v1 for Lidarr) API call to retrieve health check issues.
    async getHealth(): Promise<HealthCheck[]> {
      return this.request<HealthCheck[]>('/health');
    }
  • src/index.ts:143-151 (registration)
    The tool registration for lidarr_get_health (generated dynamically via addConfigTools). Created when Lidarr is configured, adding the tool with name 'lidarr_get_health', empty input schema, and description.
    {
      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: [],
      },
    },
Behavior3/5

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

No annotations provided. The description states 'shows any problems detected', implying a read-only informational operation but does not explicitly declare it non-destructive or detail side effects. With no annotations, the description carries burden but is minimal.

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?

Single sentence, front-loaded with verb, 14 words, no fluff. Every word earns its place.

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 zero-parameter tool with no output schema, the description explains purpose and source. However, it lacks examples of issues or return format, which could enhance completeness. Still adequate.

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 additional parameter meaning beyond the empty schema. Baseline is 3 per high coverage rule.

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 verb 'Get' and resource 'health check warnings and issues', specifying it's from Lidarr (Music). This distinguishes it from sibling health tools for Radarr/Sonarr. No tautology.

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?

The description implies usage for checking problems but offers no explicit guidance on when to use versus alternatives (e.g., other lidarr tools or other health tools). Usage is inferred from purpose.

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