Overview

Tool Name

storage_manager

Purpose

The storage_manager tool centralizes long-term file storage. List and search libraries, rename and move files, create folders, and clean up space with safety controls like confirmations and optional backups.

Key Features & Functions

Browse Persistent Storage

Explore directories and files with filters for path, name, type, and date.

Search at Scale

Find files by name, content, or metadata with result limits and scoring.

Organize & Rename

Restructure folders and rename files to keep libraries clean.

Move & Create

Move batches of files and create directories with parent auto-creation.

Monitor Usage

Retrieve storage usage and quota details for planning and governance.

Clean Up Safely

Delete with confirmations and optional backups to avoid accidental loss.
Start with LIST_FILES or SEARCH_FILES to scope changes, then organize with RENAME_FILE, MOVE_FILES, or DELETE_FILES.

Input Parameters for Each Function

All operations are routed through _storage_manager with an action value.

LIST_FILES

Parameters
NameDefinitionFormat
directory_pathDirectory to list. Defaults to the storage root.String
file_patternFilename pattern to match.String
recursiveInclude subdirectories when listing.Boolean
sort_bySort criteria: name, size, date, type.String
limitMax number of files to return.Integer

SEARCH_FILES

Parameters
NameDefinitionFormat
search_queryTerms or criteria to search for.String
search_typename, content, metadata, or all.String
file_typesRestrict to extensions or MIME groups.Array
date_rangeFilter by modified date range.Object
size_rangeFilter by file size range.Object
max_resultsMax results to return.Integer
Use search_type = "metadata" when you have rich tags or attributes indexed for your files.

RENAME_FILE

Parameters
NameDefinitionFormat
current_pathFull current file path.String
new_nameNew filename to assign.String
preserve_extensionKeep the original extension.Boolean

MOVE_FILES

Parameters
NameDefinitionFormat
source_pathsOne or more files to move.Array
destination_directoryTarget directory.String
overwrite_existingReplace files if they exist at destination.Boolean

CREATE_DIRECTORY

Parameters
NameDefinitionFormat
directory_pathPath for the new directory.String
create_parentsAuto-create missing parent folders.Boolean

DELETE_FILES

Parameters
NameDefinitionFormat
file_pathsFiles to delete.Array
confirm_deletionMust be true to proceed.Boolean
backup_before_deleteCreate a backup before deletion.Boolean

GET_STORAGE_INFO

Parameters
NameDefinitionFormat
include_usageInclude current usage stats.Boolean
include_quotasInclude quota information.Boolean

Use Cases

  1. Manage long-term archives of reports and analysis outputs for future reference.
  2. Organize mission documentation and assets into shared, persistent libraries.
  3. Clean up obsolete or duplicate files to free space across projects.
  4. Search historical data files and notebooks for research and audits.
  5. Keep backup copies of critical configuration files and templates.
  6. Publish shared resources and templates for reuse across teams.
  7. Maintain compliant archives for governance and audit needs.

Workflow/How It Works

  1. Discover with LIST_FILES or SEARCH_FILES to identify targets.
  2. Organize using RENAME_FILE, MOVE_FILES, and CREATE_DIRECTORY.
  3. Govern by checking GET_STORAGE_INFO for usage and quotas.
  4. Clean up with DELETE_FILES using confirmations and optional backups.
  5. Repeat as libraries evolve, using filters to keep operations focused.

Integration Relevance

  • file_manager_tools for end-to-end lifecycle management and attachments.
  • project_manager_tools to align storage with missions and todos.
  • artifact_manager_tools to archive generated outputs.
  • document_index_tools to index stored documents for semantic search.
  • git_action when versioning stored files or promoting templates.
Deletions are destructive. Set confirm_deletion = true only after you have reviewed the target list, and enable backup_before_delete for critical content.

Configuration Details

  • Use consistent path separators and naming conventions across teams.
  • Tailor file_pattern, date, and size filters to reduce result sets.
  • Ensure directory creation follows your organization’s structure and permissions.
  • Apply backups for regulated or business-critical content before bulk changes.
  • Align sort and limit options with UI or API consumer expectations.

Limitations or Notes

  1. File deletion is permanent unless a backup is created first.
  2. Large operations can take time and may consume significant resources.
  3. Search speed depends on indexing and storage size.
  4. Access and visibility follow workspace permissions and security policies.
  5. Quotas may block writes or moves if free space is low.
  6. Network or remote storage can affect latency and reliability.
  7. Concurrent operations may conflict and require retries.

Output

  • Listings
    Arrays of files with name, size, type, modified date, and path.
  • Search Results
    Matched files with relevance scoring and snippets.
  • Rename or Move
    Confirmations with old and new paths.
  • Create Directory
    Confirmation with path and permissions.
  • Delete
    Confirmation with optional backup reference.
  • Storage Info
    Usage and quota metrics for capacity planning.
  • Errors
    Actionable messages for permission, path, or conflict issues.