Skip to main content
Glama
YanceyOfficial

Obsidian iCloud MCP

move_file

Move or rename files and directories within Obsidian iCloud vaults. Specify source and destination paths to transfer files across directories or rename them in-place.

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
destinationYes
sourceYes

Implementation Reference

  • The core handler function for the 'move_file' tool. It validates input using MoveFileArgsSchema and uses Node.js fs.rename to move the file from source to destination path.
    export async function moveFile(args?: Record<string, unknown>) {
      const parsed = MoveFileArgsSchema.safeParse(args)
      if (!parsed.success) {
        throw new Error(`Invalid arguments for move_file: ${parsed.error}`)
      }
      await fs.rename(parsed.data.source, parsed.data.destination)
      return {
        content: [
          {
            type: 'text',
            text: `Successfully moved ${parsed.data.source} to ${parsed.data.destination}`
          }
        ]
      }
    }
  • Zod schema defining the input arguments for the move_file tool: source (current path) and destination (new path) as strings.
    export const MoveFileArgsSchema = z.object({
      source: z.string(),
      destination: z.string()
    })
  • src/index.ts:153-156 (registration)
    Registers the 'move_file' tool in the MCP server's ListToolsRequestSchema response, providing name, description prompt, and JSON schema from MoveFileArgsSchema.
      name: 'move_file',
      description: moveFileDirectoryPrompt(),
      inputSchema: zodToJsonSchema(MoveFileArgsSchema) as ToolInput
    },
  • Dispatch handler in the CallToolRequestSchema switch statement that invokes the moveFile function with parsed arguments.
    case 'move_file': {
      return moveFile(args)
    }
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: the operation fails if destination exists, works across directories, and requires allowed directories. However, it doesn't mention permissions needed, whether changes are reversible, error handling details, or rate limits, leaving gaps for a mutation tool.

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 appropriately sized and front-loaded, with every sentence earning its place: first states core function, second explains capabilities, third covers failure condition, fourth adds scope details, fifth sets constraints. No wasted words.

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

Completeness3/5

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

Given no annotations, 0% schema coverage, and no output schema, the description is moderately complete. It covers purpose, basic behavior, and constraints, but lacks details on permissions, error responses, or return values, which are important for a mutation tool with undocumented parameters.

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?

Schema description coverage is 0%, so the description must compensate. It explains that 'source' and 'destination' parameters represent file/directory paths for moving/renaming, adding meaning beyond the bare schema. However, it doesn't specify path formats or examples, leaving some ambiguity.

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 purpose with specific verbs ('move or rename files and directories') and resources ('files and directories'), distinguishing it from siblings like 'create_directory', 'edit_file', or 'remove_file'. It explicitly covers both moving between directories and renaming within the same directory.

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 for when to use this tool (moving/renaming files/directories) and mentions constraints ('destination exists, operation will fail', 'within allowed directories'). However, it doesn't explicitly state when NOT to use it or name alternatives among siblings (e.g., 'write_file' for editing content vs. renaming).

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/YanceyOfficial/obsidian-mcp'

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