Skip to main content
Glama

Move path

move_path
Destructive

Move or rename files or directories in a workspace, optionally overwriting a target file and creating missing parent directories. Use it to relocate paths without copying or deleting them.

Instructions

Move or rename a file or directory inside the workspace. overwrite=true replaces an existing file, never a directory; create_dirs (default true) makes missing parents of to. Use when: you rename or relocate files or folders. Not undoable: take a snapshot first when they are not in git. Avoid when: you duplicate (copy_path) or remove (delete_path). Output: from, to, kind, overwritten, entries, bytes. Missing source gives not_found, an existing target without overwrite gives conflict.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "move_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesNew workspace path: the final name, not a parent directory.
fromYesExisting workspace path to move or rename.
reasonNoOptional why (max 400 chars), audit-logged.
overwriteNotrue replaces an existing target file (default false). A directory is never replaced.
create_dirsNotrue creates missing parent directories of `to` (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv4.5.0
    • removedInput schema / properties / create_dirs / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "maximum": 1,
      -    "minimum": 0,
      -    "type": "integer"
      -  }
      -]
    • changedInput schema / properties / create_dirs / description
      Previous value: -"1 creates missing parent directories of `to` (default 1)."New value: +"true creates missing parent directories of `to` (default true)."
    • removedInput schema / properties / create_dirs / maximum
      Removed value: -1
    • removedInput schema / properties / create_dirs / minimum
      Removed value: -0
    • changedInput schema / properties / create_dirs / type
      Previous value: -"integer"New value: +"boolean"
    • removedInput schema / properties / overwrite / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "maximum": 1,
      -    "minimum": 0,
      -    "type": "integer"
      -  }
      -]
    • changedInput schema / properties / overwrite / description
      Previous value: -"1 replaces an existing target file (default 0). A directory is never replaced."New value: +"true replaces an existing target file (default false). A directory is never replaced."
    • removedInput schema / properties / overwrite / maximum
      Removed value: -1
    • removedInput schema / properties / overwrite / minimum
      Removed value: -0
    • changedInput schema / properties / overwrite / type
      Previous value: -"integer"New value: +"boolean"
  2. Addedv4.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, readOnlyHint=false): it discloses irreversibility, the recommended snapshot mitigation, that directories are never overwritten, the create_dirs default, returned fields, and the not_found/conflict error conditions. This is the exact class of context annotations cannot carry.

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?

Front-loaded with the core action, then compact labeled clauses (Use when / Avoid when / Output) that are each scannable. No filler sentences; even the output-field list earns its place since there is no output schema.

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

Completeness5/5

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

For a 5-parameter destructive mutation with no output schema, the description covers safety, side effects, defaults, return shape, and failure modes. An agent has everything needed to invoke it correctly and to decide whether to snapshot first.

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 coverage is 100%, so overwrite and create_dirs are already fully documented, and the description largely restates them. It adds a small amount of framing (create_dirs defaults true, overwrite applies to files only) but nothing about `reason` or `to` beyond the schema's own 'final name, not a parent directory' note.

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?

States a specific verb pair and resource: 'Move or rename a file or directory inside the workspace.' This immediately separates it from copy_path and delete_path, named explicitly later, so an agent can pick it without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit 'Use when' (rename or relocate files/folders) and 'Avoid when' (duplicate -> copy_path, remove -> delete_path) routing. It also adds a prerequisite-style caution: not undoable, take a snapshot first when not in git.

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