Skip to main content
Glama
Sign In
WinDirStat MCP Server

WinDirStat MCP Server

by harezadmm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

clean_safe_targets

Delete specified temporary cache folders or files safely by providing absolute paths and confirming the action, with built-in protection guards to prevent accidental deletion.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "targets": "<targets>",
      "confirmAction": "<confirmAction>"
    },
    "name": "clean_safe_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetsYesArray of absolute file or directory paths to clean
confirmActionYesMust be true to execute deletion

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description must detail behavior. It mentions 'safely delete' and 'built-in protection guards' but does not specify what protections exist (e.g., path validation, confirmation required), the actual deletion behavior, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence conveying the core purpose without extraneous words. Efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations or output schema, the description should provide more context about return value, error handling, and detailed behavior. It only gives a high-level action, leaving significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear parameter descriptions. The description adds minimal extra meaning (hints at safety via confirmAction) but does not substantially improve understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it deletes temporary cache folders/files with safety features. The verb 'delete' and resource 'temporary cache folders or files' are specific. Siblings are scanning, listing, and categorizing tools, making this distinct.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. The description implies a scenario (cleaning temporary files) but does not state prerequisites, when not to use, or how to decide among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools