disk-cleanup
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_largeA | 列出指定目录下体积大于 min_mb MB 的文件，按大小降序返回前 top_n 个。 |
| scan_duplicatesA | 按内容 hash 找出重复文件，按重复组返回（含可释放空间估算）。 先按文件大小初筛，仅对"大小相同"的文件做内容 hash，性能更友好。 |
| scan_by_extB | 按文件后缀扫描（默认扫常见垃圾后缀 .tmp/.log/.cache/.bak/.old）。 |
| scan_oldB | 扫描多久未修改过的文件（默认 90 天）。 |
| summarizeB | 目录体检：总大小、文件数、按类型（后缀）占比 Top10。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a uniquely identifiable scan dimension: large files, duplicates, extension-based, old files, and summary. Even the four scan_* tools are clearly distinct by their filtering criteria, leaving no real ambiguity for an agent.
The scan_* prefix creates a predictable pattern for the four scanning tools, and the criterion is clear in each name. summarize deviates from the prefix pattern but is still a sensible, readable action name rather than a random inconsistency.
Five tools is well-scoped for a disk cleanup helper: the main scan dimensions are covered, and there is no redundant bloat. The set feels complete enough to be useful without overwhelming an agent.
The server can identify cleanup candidates but offers no cleanup action such as delete or move-to-trash, so an agent cannot complete an actual disk cleanup workflow. This is a significant functional gap given the server name and stated purpose.