tidy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIDY_HOME | No | Directory for plans and undo logs (default: ~/.tidy). | |
| TIDY_LIMIT | No | Maximum number of files per run (default: 500). Can also be set in ~/.tidy/config.toml as limit. | |
| TIDY_IGNORE | No | File name patterns to leave alone, e.g. "*.part,keep-*". Can also be set in ~/.tidy/config.toml as ignore. | |
| TIDY_WORKERS | No | Number of files to describe at once (default: 4). Can also be set in ~/.tidy/config.toml as workers. | |
| TIDY_TEXT_MODEL | No | Ollama model for text files (default: qwen2.5:7b). Can also be set in ~/.tidy/config.toml as text_model. | |
| TIDY_VISION_MODEL | No | Ollama model for image files (default: qwen2.5vl:7b). Can also be set in ~/.tidy/config.toml as vision_model. |
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 |
|---|---|
| scan_folderA | List the files tidy would look at in a folder (top level only, no hidden files). |
| describe_fileB | Ask the local model for a better name and folder for one file. |
| plan_tidyB | Build a dry-run plan for a folder. Nothing is moved. Show the plan to the user. |
| apply_planA | Apply a plan the user has approved. Files are moved, never deleted. |
| undoA | Put every file from an applied plan back where it was. |
| find_duplicatesC | Groups of identical files. The first in each group is the original and is kept. |
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 6 tools
Each tool targets a distinct granularity and action: scan_folder (inventory), describe_file (single-file suggestion), plan_tidy (folder dry-run), apply_plan (execution), undo (reversal), find_duplicates (dedup). No two tools could plausibly be swapped for the same task.
Five of six tools follow a clean verb_noun pattern (scan_folder, describe_file, plan_tidy, apply_plan, find_duplicates). The lone outlier is 'undo', which breaks the pattern but is a universally understood primitive verb.
Six tools is well-scoped for a file-tidying assistant: one inventory, one per-file helper, one planning step, one apply step, one undo, and dedup detection. Each earns its place with no filler.
The surface covers the full safe lifecycle (scan, plan, apply, undo) plus duplicate handling, which is strong for the domain. Minor gaps remain: no way to list past plans or selectively roll back a single file, and no configuration of naming rules.