Skip to main content
Glama

prowlarr_get_stats

Retrieve indexer performance statistics including queries, grabs, and failures to monitor search reliability and track download activity.

Instructions

Get indexer statistics (queries, grabs, failures)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler: checks if Prowlarr client configured, calls getIndexerStats(), formats stats with counts, per-indexer details, and totals into JSON response
    case "prowlarr_get_stats": {
      if (!clients.prowlarr) throw new Error("Prowlarr not configured");
      const stats = await clients.prowlarr.getIndexerStats();
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: stats.indexers.length,
            indexers: stats.indexers.map(s => ({
              name: s.indexerName,
              queries: s.numberOfQueries,
              grabs: s.numberOfGrabs,
              failedQueries: s.numberOfFailedQueries,
              failedGrabs: s.numberOfFailedGrabs,
              avgResponseTime: s.averageResponseTime + 'ms',
            })),
            totals: {
              queries: stats.indexers.reduce((sum, s) => sum + s.numberOfQueries, 0),
              grabs: stats.indexers.reduce((sum, s) => sum + s.numberOfGrabs, 0),
              failedQueries: stats.indexers.reduce((sum, s) => sum + s.numberOfFailedQueries, 0),
              failedGrabs: stats.indexers.reduce((sum, s) => sum + s.numberOfFailedGrabs, 0),
            },
          }, null, 2),
        }],
      };
    }
  • Tool schema: defines name, description, and empty input schema (no parameters required)
      name: "prowlarr_get_stats",
      description: "Get indexer statistics (queries, grabs, failures)",
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    }
  • src/index.ts:535-579 (registration)
    Tool registration: adds prowlarr_get_stats to TOOLS array conditionally if Prowlarr client is configured
    if (clients.prowlarr) {
      TOOLS.push(
        {
          name: "prowlarr_get_indexers",
          description: "Get all configured indexers in Prowlarr",
          inputSchema: {
            type: "object" as const,
            properties: {},
            required: [],
          },
        },
        {
          name: "prowlarr_search",
          description: "Search across all Prowlarr indexers",
          inputSchema: {
            type: "object" as const,
            properties: {
              query: {
                type: "string",
                description: "Search query",
              },
            },
            required: ["query"],
          },
        },
        {
          name: "prowlarr_test_indexers",
          description: "Test all indexers and return their health status",
          inputSchema: {
            type: "object" as const,
            properties: {},
            required: [],
          },
        },
        {
          name: "prowlarr_get_stats",
          description: "Get indexer statistics (queries, grabs, failures)",
          inputSchema: {
            type: "object" as const,
            properties: {},
            required: [],
          },
        }
      );
    }
  • ProwlarrClient helper: performs API GET request to /indexerstats endpoint to retrieve raw indexer statistics
     * Get indexer statistics
     */
    async getIndexerStats(): Promise<{ indexers: IndexerStats[] }> {
      return this['request']<{ indexers: IndexerStats[] }>('/indexerstats');
    }
  • TypeScript interface defining the structure of indexer stats data returned from Prowlarr API
    export interface IndexerStats {
      id: number;
      indexerId: number;
      indexerName: string;
      averageResponseTime: number;
      numberOfQueries: number;
      numberOfGrabs: number;
      numberOfRssQueries: number;
      numberOfAuthQueries: number;
      numberOfFailedQueries: number;
      numberOfFailedGrabs: number;
      numberOfFailedRssQueries: number;
      numberOfFailedAuthQueries: number;
    }
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. It states it's a read operation ('Get'), which implies non-destructive, but doesn't disclose behavioral traits like authentication needs, rate limits, or response format. The description is minimal and lacks critical operational context.

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 that front-loads the purpose without any fluff. Every word earns its place, making it highly concise and well-structured for a simple tool.

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 minimal. It covers the basic purpose but lacks details on behavior, output format, or integration context, which could be helpful for an AI agent despite the low complexity.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. Baseline is 4 for zero parameters, as it avoids unnecessary complexity.

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 action ('Get') and the resource ('indexer statistics'), with specific metrics listed (queries, grabs, failures). It distinguishes from most siblings by focusing on Prowlarr stats rather than other *arr services, though it doesn't explicitly differentiate from 'prowlarr_get_indexers' which might share similar context.

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?

No guidance on when to use this tool versus alternatives like 'prowlarr_get_indexers' or other *arr status tools. The description implies it's for retrieving statistical data, but lacks explicit context on use cases 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