Skip to main content
Glama
Wayazi

MCP File System

by Wayazi

move_file

Transfer files securely between directories on the MCP File System by specifying source and destination paths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destinationYesDestination path
sourceYesSource path

Implementation Reference

  • src/index.ts:126-148 (registration)
    Full registration of the 'move_file' MCP tool, including schema definition and inline handler function.
    server.tool(
        "move_file",
        { source: z.string().describe("Source path"), destination: z.string().describe("Destination path") },
        async ({ source, destination }: { source: string, destination: string }) => {
            try {
                const validSource = validatePath(source);
                const validDest = validatePath(destination);
                
                // Check if destination exists
                try {
                    await fs.access(validDest);
                    throw new Error('Destination already exists');
                } catch (error: any) {
                    if (error.code !== 'ENOENT') throw error;
                }
    
                await fs.rename(validSource, validDest);
                return { content: [{ type: 'text', text: `Moved successfully: ${source} -> ${destination}` }] };
            } catch (error: any) {
                return { content: [{ type: 'text', text: `Error moving file/directory: ${error.message}` }] };
            }
        }
    );
  • Handler implementation for 'move_file' tool: validates paths using validatePath, ensures destination doesn't exist, performs fs.rename to move source to destination, and returns success/error text content.
    async ({ source, destination }: { source: string, destination: string }) => {
        try {
            const validSource = validatePath(source);
            const validDest = validatePath(destination);
            
            // Check if destination exists
            try {
                await fs.access(validDest);
                throw new Error('Destination already exists');
            } catch (error: any) {
                if (error.code !== 'ENOENT') throw error;
            }
    
            await fs.rename(validSource, validDest);
            return { content: [{ type: 'text', text: `Moved successfully: ${source} -> ${destination}` }] };
        } catch (error: any) {
            return { content: [{ type: 'text', text: `Error moving file/directory: ${error.message}` }] };
        }
    }
  • Zod input schema for 'move_file' tool defining 'source' and 'destination' as strings.
    { source: z.string().describe("Source path"), destination: z.string().describe("Destination path") },
  • Shared helper function validatePath used by move_file (and other tools) to ensure paths are within allowed directories before operations.
    function validatePath(filePath: string): string {
        const absolutePath = path.resolve(filePath);
        if (!allowedDirs.some(dir => absolutePath.startsWith(path.resolve(dir)))) {
            throw new Error(`Access denied: ${filePath} is not within allowed directories`);
        }
        return absolutePath;
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Related 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/Wayazi/mcp_file_system'

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