Disk Clean MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_os_env_pathsA | OSに応じた代表的なキャッシュ・ログディレクトリのうち、実在するものを返す。 掃除対象の場所をユーザーが指定していないときの候補探しに使う。 |
| analyze_disk_usageA | 指定ディレクトリ配下の容量内訳を返す（読み取りのみ）。 カテゴリ別合計（dev_cache/video/log/other）と、深さ max_depth までのエントリのうち 大きい順の上位を含む。各エントリのサイズは配下の合計なので、親子のサイズは重複する。 どこが大きいか分かったら、そのパスを指定して再度呼ぶと効率よく掘り下げられる。 |
| scan_cleanup_targetsA | 条件に一致する削除候補をサイズの大きい順に列挙する（Dry-Run。何も削除しない）。 返された scan_id は move_to_trash に必要。結果はユーザーに提示して同意を得ること。 |
| move_to_trashA | 指定パスをOSのゴミ箱（Trash/Recycle Bin）へ移動する。完全削除はしない。 必ずユーザーの明示的な同意を得てから実行すること。 スキャン結果にないパスや保護パスは skip される。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| cleanup_workflow | ディスククリーンアップを安全な手順で進めるためのプロンプト。 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct stage: env-path discovery, read-only size analysis, dry-run candidate scanning, and the actual trash move. analyze_disk_usage and scan_cleanup_targets both traverse directories and return sizes, which could be momentarily confused, but the descriptions clearly separate breakdown analysis from deletion-candidate listing with the required scan_id.
All four tools follow the same snake_case verb_noun convention (get_os_env_paths, analyze_disk_usage, scan_cleanup_targets, move_to_trash). Verb choice is descriptive and consistent across the set.
Four tools is on the lean side but each maps to a necessary step in the cleanup workflow with no redundancy. A slightly richer surface (e.g. trash listing/restore) would round it out, but nothing here feels superfluous.
The core lifecycle (discover candidate locations → analyze sizes → scan for deletable items → move to trash with consent) is fully covered, including a safety-first dry-run step. Gaps exist around undo/restore-from-trash and inspection of what was moved, but agents can work around these with OS-level operations.