Skip to main content
Glama

Move File

move_file
Destructive

Moves or renames files and directories within allowed folders in a single operation. Use it to relocate a path or change its name; the call fails 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.

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": {
      "source": "<source>",
      "destination": "<destination>"
    },
    "name": "move_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesThe file or directory to move or rename. Absolute, or relative to an allowed directory; it must resolve inside the allowed directories.
destinationYesIts new path, including the name; nothing may exist there yet. Absolute, or relative to an allowed directory; it must resolve inside the allowed directories.

Output Schema

NameRequiredDescriptionDefault
contentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag the operation as destructive and non-idempotent, and the description adds real value on top: it states that a pre-existing destination causes failure and that both paths must resolve inside allowed directories. What is not stated is that the source is removed as a result, though the destructiveHint annotation covers the safety implication.

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

Conciseness4/5

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

The description is short and front-loaded with the core action, and the failure condition is easy to spot. The fourth sentence largely repeats the second (cross-directory moves plus same-directory renames), which is mild redundancy rather than a structural flaw.

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?

With rich annotations, complete schema documentation, and an output schema, the description covers the constraints an agent needs: source/destination scoping and the conflict-on-existing-destination rule. For a two-parameter mutation tool this is close to complete.

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 both source and destination are already fully documented in the schema, including the allowed-directory resolution rule. The description restates the destination-must-not-exist constraint but adds no path syntax or naming details beyond structured data.

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

Purpose4/5

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

The description uses a specific verb and resource ("Move or rename files and directories") and clarifies that move and rename are the same operation with different scope. It does not explicitly distinguish itself from the closest sibling, copy_file, so an agent must infer that distinction from the verb alone.

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

Usage Guidelines3/5

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

Usage is implied by the operation described, and the failure-on-existing-destination rule helps an agent decide when the call will succeed. There is no explicit when-to-use versus when-to-use-copy_file guidance or mention of alternatives, leaving routing to inference.

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