Skip to main content
Glama

arr_get_status

Check connection status of Sonarr and Radarr to confirm media automation services are operational.

Instructions

Check connection status of Sonarr and Radarr services

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler function that checks connection status of both Sonarr and Radarr services. It calls getSystemStatus() on each client, catches errors, and returns availability info.
    async arrGetStatus(): Promise<Record<string, unknown>> {
      const results: Record<string, unknown> = {};
    
      const sonarrResult = await (async () => {
        try {
          const client = this.ensureSonarr();
          const status = await client.getSystemStatus();
          return { available: true, version: status.version, appName: status.appName };
        } catch (error) {
          return {
            available: false,
            error: error instanceof Error ? error.message : String(error),
          };
        }
      })();
    
      const radarrResult = await (async () => {
        try {
          const client = this.ensureRadarr();
          const status = await client.getSystemStatus();
          return { available: true, version: status.version, appName: status.appName };
        } catch (error) {
          return {
            available: false,
            error: error instanceof Error ? error.message : String(error),
          };
        }
      })();
    
      const [sonarr, radarr] = await Promise.allSettled([sonarrResult, radarrResult]);
    
      results.sonarr = sonarr.status === "fulfilled" ? sonarr.value : { available: false, error: "Check failed" };
      results.radarr = radarr.status === "fulfilled" ? radarr.value : { available: false, error: "Check failed" };
    
      return {
        success: true,
        services: results,
      };
    }
  • Schema definition for arr_get_status - a cross-service tool with no input parameters.
    export const ARR_CROSS_TOOL_SCHEMAS = [
      {
        name: "arr_get_status",
        description: "Check connection status of Sonarr and Radarr services",
        inputSchema: { type: "object" as const, properties: {} },
      },
    ];
  • Registration of arr_get_status in the tool registry, delegating to arrFunctions.arrGetStatus().
    registry.register("arr_get_status", () =>
      arrFunctions.arrGetStatus().then(wrapResponse)
    );
Behavior2/5

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

The description does not disclose what the output is, whether the tool is idempotent, or how it behaves if services are unreachable. With no annotations, the description fails to provide essential behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no unnecessary words. It could be slightly more informative, but it is well-structured.

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 the tool has no parameters, no output schema, and no annotations, the description is too brief. It lacks information about return values, error behavior, or any side effects, making it incomplete for an AI agent to use confidently.

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?

There are zero parameters, and schema coverage is 100%. The description adds minor value by specifying the services (Sonarr and Radarr), so the baseline of 3 is appropriate.

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 tool checks connection status of Sonarr and Radarr services, using a specific verb and resource. No sibling tool has a similar purpose, so differentiation is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, when not to use it, or any prerequisites. The description is minimal and lacks usage context.

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/niavasha/plex-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server