Skip to main content
Glama
harezadmm

WinDirStat MCP Server

by harezadmm

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
scan_directoryB

Deep scan a directory and return subdirectories sorted by storage size in MB/GB with file counts.

get_largest_itemsA

Find top N largest files and subfolders under a specific path.

categorize_safety_tiersB

Categorize directory items into Tier 1 (100% Safe Cache/Temp), Tier 2 (Reviewable Downloads/Media), and Tier 3 (Protected Code/Projects).

clean_safe_targetsC

Safely delete specified temporary cache folders or files with built-in protection guards.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: scanning, finding large items, categorizing by safety, and cleaning. No overlap or ambiguity.

Naming Consistency5/5

All tools use snake_case with a consistent verb_noun pattern (e.g., scan_directory, categorize_safety_tiers), making predictions easy.

Tool Count5/5

With only 4 tools, the server is well-scoped for disk cleanup. Each tool adds essential functionality without redundancy or bloat.

Completeness4/5

The tools cover a logical workflow from scanning to cleaning. Minor gap: no tool to view or manage individual files beyond the clean operation, but the surface is sufficient for the domain.

Maintenance

ActivitySlowing
ResponsivenessNo issues