No user-submitted related servers found.
Scored across 9 tools
The three inspect_* tools are cleanly separated by resource (memory, storage, hardware), and the plan/apply/purge flow is explicit about which step mutates state. The only soft boundary is rollback vs. recover, both of which restore files, but the descriptions distinguish completed-plan rollback from repairing interrupted moves.
Most names follow a verb_noun pattern (inspect_memory, plan_cleanup, apply_plan, list_quarantine, purge_quarantine), with consistent snake_case throughout. The bare verbs 'rollback' and 'recover' are the only deviations, and they remain unambiguous.
Nine tools map exactly onto the disk-cleanup lifecycle: three inspectors, plan, apply, quarantine listing, purge, rollback, and recovery. No tool feels redundant or missing from the count perspective.
The surface covers the full inspect → plan → apply → quarantine → purge/rollback/recover lifecycle, including non-reversible and interrupted-operation paths. Minor gaps: there is no tool to list or discard a stored but unapplied plan, and cleanup roots appear to be configuration-only rather than inspectable/modifiable.
