Skip to main content
Glama

prowlarr_test_indexers

Test all indexers to check their health status and ensure they are working properly for media management applications.

Instructions

Test all indexers and return their health status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main tool handler in the MCP server request handler switch statement. Calls ProwlarrClient.testAllIndexers() and getIndexers(), maps indexer names, formats results as JSON with counts of healthy/failed indexers.
    case "prowlarr_test_indexers": {
      if (!clients.prowlarr) throw new Error("Prowlarr not configured");
      const results = await clients.prowlarr.testAllIndexers();
      const indexers = await clients.prowlarr.getIndexers();
      const indexerMap = new Map(indexers.map(i => [i.id, i.name]));
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: results.length,
            indexers: results.map(r => ({
              id: r.id,
              name: indexerMap.get(r.id) || 'Unknown',
              isValid: r.isValid,
              errors: r.validationFailures.map(f => f.errorMessage),
            })),
            healthy: results.filter(r => r.isValid).length,
            failed: results.filter(r => !r.isValid).length,
          }, null, 2),
        }],
      };
    }
  • Tool schema definition: no input parameters required.
      name: "prowlarr_test_indexers",
      description: "Test all indexers and return their health status",
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • src/index.ts:561-568 (registration)
    Tool registration in the TOOLS array, conditionally added if Prowlarr client is configured.
      name: "prowlarr_test_indexers",
      description: "Test all indexers and return their health status",
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • ProwlarrClient.testAllIndexers() method: sends POST request to Prowlarr API /indexer/testall to test all configured indexers.
    async testAllIndexers(): Promise<Array<{ id: number; isValid: boolean; validationFailures: Array<{ propertyName: string; errorMessage: string }> }>> {
      return this['request']<Array<{ id: number; isValid: boolean; validationFailures: Array<{ propertyName: string; errorMessage: string }> }>>('/indexer/testall', { method: 'POST' });
    }
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 states the tool tests indexers and returns health status, but lacks details on what 'test' entails (e.g., connectivity checks, authentication validation), potential side effects (e.g., rate limiting, logging), error handling, or output format. This is a significant gap for a tool with no annotation coverage.

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 a single, efficient sentence: 'Test all indexers and return their health status.' It's front-loaded with the core purpose, has zero waste, and is appropriately sized for a simple tool with no parameters.

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

Completeness2/5

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

Given no annotations, no output schema, and 0 parameters, the description is minimal. It states the purpose but lacks completeness for a testing tool: it doesn't explain what 'health status' includes (e.g., success/failure, latency metrics), how results are structured, or any behavioral context like execution time or side effects. This is inadequate for guiding an agent effectively.

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, and it correctly doesn't mention any. Baseline for 0 parameters is 4, as it avoids unnecessary parameter discussion.

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: 'Test all indexers and return their health status.' It specifies the verb ('test'), resource ('indexers'), and outcome ('health status'). However, it doesn't explicitly differentiate from sibling tools like 'prowlarr_get_indexers' or 'prowlarr_get_stats', which might provide related indexer information without testing functionality.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing (e.g., after configuration changes), or how it differs from siblings like 'prowlarr_get_indexers' (which might list indexers without testing) or 'prowlarr_get_stats' (which might provide statistics). Usage is implied only by the purpose statement.

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