Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

move_path

Destructive

Move or rename a workspace file or folder using relative source and destination paths, with local panel approval and no overwrites.

Instructions

Move/rename a workspace file or folder, after approval in the local panel. No overwrites.

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
toYesDestination relative path
fromYesSource relative path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds genuine context beyond them: an approval-gate requirement before execution and a no-overwrite guarantee that tells the agent the operation will not silently clobber an existing destination.

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?

Two short clauses, zero filler, with the approval constraint and the overwrite constraint both front-loaded where an agent will read them.

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 two-parameter, no-output-schema tool with destructive annotations already supplied, the key risks are covered: approval requirement and non-overwrite behavior. Minor gaps remain around directory recursion and the success response shape, but nothing that would cause a misinvocation.

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% with clear relative-path descriptions for both from and to, so the schema carries parameter meaning. The description adds nothing about path semantics (relative to workspace root, folder recursion, trailing slashes), so the baseline 3 applies.

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?

States a specific verb pair (move/rename) and resource (workspace file or folder), which an agent can distinguish from delete_path or edit_lines. It stops short of naming an explicit sibling, but the operation is unambiguous.

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?

"After approval in the local panel" gives a real precondition for invocation, and "No overwrites" implies a failure case. However, there is no statement of when to prefer this over e.g. replace_exact for in-place edits, or what to do if the destination already exists.

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