Skip to main content
Glama
kridaydave

File Organizer MCP

by kridaydave

Smart Organize Files

file_organizer_organize_smart
Destructive

Organize mixed file collections by type: sort music into artist/album folders, photos into date-based folders with optional GPS removal, and documents into topic folders. Preview changes with dry_run.

Instructions

Automatically organizes mixed files (music, photos, documents) using the appropriate strategy for each type. Music → Artist/Album structure. Photos → Date-based folders with optional GPS stripping. Documents → Topic-based folders. Use dry_run=true to preview changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoIf true, only preview changes without moving files
recursiveNoScan subdirectories recursively
strip_gpsNoStrip GPS location data from photos for privacy
source_dirYesFull path to the directory containing mixed files (music, photos, documents)
target_dirYesFull path to the directory where organized files will be placed
music_structureNoFolder structure for music filesartist/album
create_shortcutsNoFor multi-topic documents, create shortcuts in additional topic folders
photo_date_formatNoDate format for photo folder structureYYYY/MM
copy_instead_of_moveNoCopy files instead of moving them
photo_group_by_cameraNoGroup photos by camera model within date folders
Install Server

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate destructiveness, and the description adds useful behavioral context: the type-specific strategies, optional GPS stripping, and the dry_run preview flag. It does not contradict annotations and provides additional insight beyond the structured metadata.

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?

The description is compact, front-loading the core purpose, then detailing strategies, and ending with a safety tip. Every sentence contributes meaning without redundancy.

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

Completeness4/5

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

For a complex tool with 10 parameters and destructive behavior, the description covers the main workflow and preview mode. It omits details like copy vs. move or recursion, but those are in the schema, and the high-level behavior is adequately explained.

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

Parameters4/5

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

While schema coverage is 100%, the description clarifies the meaning behind key parameters like music_structure and photo_date_format by showing their strategies (Artist/Album, Date-based). This adds semantic value beyond the schema's bare descriptions.

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

Purpose5/5

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

The description clearly states the tool's function: automatically organize mixed files by type, with specific strategies for music, photos, and documents. It differentiates from sibling tools by focusing on mixed-file handling and per-type strategy selection.

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

Usage Guidelines4/5

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

The description implies the tool is for mixed files and recommends dry_run for preview, but it does not explicitly contrast with alternative tools like organize_music or organize_photos. The usage context is clear enough, though exclusions or alternatives are not stated.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kridaydave/File-Organizer-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server