Skip to main content
Glama
A-Niranjan

MCP Filesystem Server

by A-Niranjan

move_file

Move or rename files and directories within allowed paths. This tool transfers files between directories or renames them in place, failing if the destination already exists.

Instructions

Move or rename files and directories. Can move files between directories and rename them in a single operation. If the destination exists, the operation will fail. Works across different directories and can be used for simple renaming within the same directory. Both source and destination must be within allowed directories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesSource path of the file or directory to move
destinationYesDestination path where to move the file or directory

Implementation Reference

  • The main execution logic for the 'move_file' tool. Parses input arguments using the schema, validates both source and destination paths against allowed directories, creates the destination parent directory if necessary, performs the file/directory move using fs.rename, logs the operation, and returns a success message.
    case 'move_file': {
      const parsed = MoveFileArgsSchema.safeParse(a)
      if (!parsed.success) {
        throw new FileSystemError(`Invalid arguments for ${name}`, 'INVALID_ARGS', undefined, {
          errors: parsed.error.format(),
        })
      }
    
      const validSourcePath = await validatePath(parsed.data.source, config)
      const validDestPath = await validatePath(parsed.data.destination, config)
    
      // Ensure the destination parent directory exists
      const destDir = path.dirname(validDestPath)
      await fs.mkdir(destDir, { recursive: true })
    
      await fs.rename(validSourcePath, validDestPath)
      await logger.debug(`Moved file from ${validSourcePath} to ${validDestPath}`)
    
      endMetric()
      return {
        content: [
          {
            type: 'text',
            text: `Successfully moved ${parsed.data.source} to ${parsed.data.destination}`,
          },
        ],
      }
    }
  • Zod schema defining the expected input structure for the move_file tool: source (string) and destination (string) paths.
    const MoveFileArgsSchema = z.object({
      source: z.string().describe('Source path of the file or directory to move'),
      destination: z.string().describe('Destination path where to move the file or directory'),
    })
  • src/index.ts:297-305 (registration)
    Tool registration in the ListTools handler response. Specifies the tool name, detailed description of functionality and limitations, and converts the Zod schema to JSON schema for the MCP protocol.
    {
      name: 'move_file',
      description:
        'Move or rename files and directories. Can move files between directories ' +
        'and rename them in a single operation. If the destination exists, the ' +
        'operation will fail. Works across different directories and can be used ' +
        'for simple renaming within the same directory. Both source and destination must be within allowed directories.',
      inputSchema: zodToJsonSchema(MoveFileArgsSchema) as ToolInput,
    },
Behavior4/5

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

With no annotations provided, the description carries the full burden. It effectively discloses key behavioral traits: the operation can fail if destination exists, it works across directories, and both paths must be within allowed directories. It doesn't mention permissions, rate limits, or error handling details, but covers essential mutation behavior.

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 front-loaded with the core purpose and efficiently adds essential details in subsequent sentences. Every sentence adds value: operation scope, failure condition, cross-directory capability, renaming use case, and security constraint. Zero wasted words.

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 mutation tool with no annotations and no output schema, the description does well by covering purpose, constraints, and usage context. It could be more complete by mentioning what happens on success (e.g., returns confirmation) or error types, but given the tool's relative simplicity, it provides adequate contextual information.

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 description coverage is 100%, so the schema already documents both parameters. The description adds marginal value by implying that 'source' and 'destination' refer to file/directory paths for moving/renaming, but doesn't provide additional syntax or format details beyond what the schema provides.

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 specific action ('move or rename files and directories') and distinguishes it from sibling tools like 'create_directory', 'edit_file', and 'write_file' by focusing on relocation/renaming rather than creation, modification, or writing new content.

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 provides clear context on when to use it ('move files between directories', 'rename them', 'simple renaming within the same directory') and mentions constraints ('destination exists → fails', 'must be within allowed directories'). However, it doesn't explicitly state when NOT to use it or name specific alternatives among siblings.

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

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/A-Niranjan/mcp-filesystem'

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