Skip to main content
Glama

Stack health

get_stack_health
Read-only

Checks health of all configured media stack services—versions, disk space, failing health checks, last scans—and reports commands queued, running, or recently finished.

Instructions

Health of every configured service: version, disk space, failing health checks, last library scan (services ids are the valid instance values). Answers partially, with a degraded list, when a service is down. commands follows up trigger_search and trigger_scan: queued, running, and finished in the last 15 minutes, so a command not listed has finished. Profiles, root folders and tags: get_instance_options. service or instance checks one, without seedingRules. detail: "full" adds permissions, seedingRules (Cleanuparr, client and indexer seed limits and removal rules), Reclaimerr cleanup (what will be deleted or moved, and when), and each service's recent warnings and errors in logs; check lastSeen, since an old line may no longer apply. API keys are never returned. Field reference: arr://docs/get_stack_health.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_stack_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items to return.
detailNoHow much per-item detail to return.standard
serviceNo
instanceNoWhich instance (e.g. "4k") when several of this service exist. Omit it when there is one.

Output Schema

NameRequiredDescriptionDefault
logsNo
disksYes
scansYes
cleanupNo
commandsNo
degradedYes
failuresYes
servicesYes
endpointsNo
permissionsNo
seedingRulesNo
cleanuparrRemovalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.0
    • changedInput schema / properties / detail / description
      Previous value: -"How much per-item detail to return; defaults to standard."New value: +"How much per-item detail to return."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum items to return; defaults to 50, hard maximum 500."New value: +"Maximum items to return."
  2. Addedv1.84.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark it readOnly, but the description adds substantial behavior beyond that: it returns partial results with a `degraded` list when a service is down, `commands` covers only the last 15 minutes so absence means finished, and API keys are never returned (a useful security guarantee). It also discloses what `detail: full` unlocks rather than leaving that to trial and error.

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?

Information-dense and front-loaded, with no filler sentences. The telegraphic semicolon-and-parenthesis style makes it harder to parse on a first read, but every clause carries distinct operational meaning, so the density is earned rather than padded.

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

Completeness5/5

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

For a four-parameter read tool with 0 required params and an output schema, this covers everything an agent needs: scope, per-service narrowing, detail escalation, degraded-mode semantics, and a field reference pointer (arr://docs/get_stack_health) for the rest. No gaps remain that would cause a misinvocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Goes well past the 75%-covered schema: it explains that `services` ids are the valid `instance` values, that `service`/`instance` restrict the report to one service and drop `seedingRules`, and it enumerates what each higher `detail` level adds (`permissions`, `seedingRules`, Reclaimerr `cleanup`, `logs`). Only `limit` is left to the schema, which already describes it.

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?

Names the resource and its full contents concretely: version, disk space, failing health checks, last library scan, plus the `commands` queue. It also scopes itself against siblings (get_instance_options for profiles/root folders/tags) and states the single-service variant, so an agent can distinguish it from every other get_* tool without opening a schema.

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

Usage Guidelines5/5

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

Explicit routing: use get_instance_options for profiles/root folders/tags, use `service`/`instance` to check one service, and use `commands` to follow up trigger_search/trigger_scan. It even states an exclusion (single-service view omits `seedingRules`) and a reading caveat (check `lastSeen`, an old log line may no longer apply).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.