Skip to main content
Glama

prowlarr_test_indexers

Checks the health of all configured indexers and returns their status to identify connectivity issues.

Instructions

Test all indexers and return their health status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:717-724 (registration)
    Tool registration for 'prowlarr_test_indexers' in the Prowlarr tools section. Defines the tool name, description ('Test all indexers and return their health status'), and empty input schema.
      name: "prowlarr_test_indexers",
      description: "Test all indexers and return their health status",
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • Handler for 'prowlarr_test_indexers' in the CallToolRequestSchema switch statement. Calls clients.prowlarr.testAllIndexers() to POST to /indexer/testall, then maps results with indexer names and returns count of healthy/failed indexers with their validation errors.
    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),
        }],
      };
    }
  • Helper method in ProwlarrClient that performs the actual API call. Sends a POST request to /api/v1/indexer/testall endpoint and returns the validation results with isValid flag and validationFailure details.
    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, and the description fails to disclose behavioral traits such as potential performance impact, side effects, or whether it is a read-only operation, which is critical for a 'test' 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 a single, front-loaded sentence with no redundant information, achieving maximum conciseness.

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 parameterless tool with no output schema, the description adequately conveys the action and result, though it could benefit from mentioning synchronous execution or side effects.

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?

With no parameters and 100% schema coverage, the description adds value by specifying the resource 'all indexers', which is not indicated in the schema, thus clarifying the tool's scope.

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 action 'Test all indexers' and the output 'return their health status', distinguishing it from siblings like prowlarr_get_indexers which likely lists indexers.

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 health checking but does not specify when to use vs alternatives or provide any exclusions or prerequisites.

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