Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Move Path

move_path

Move or rename files and directories by specifying source and destination paths, with optional overwrite and sudo controls for authorized system tasks.

Instructions

Move/rename a file or directory.

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_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
sudoNo
sourceYes
overwriteNo
destinationYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden and does almost none of it. It does not say that an existing destination is replaced when overwrite is set, that sudo elevates privileges (a security-relevant side effect), or that the operation is irreversible for the source path. 'Move/rename' hints at mutation but leaves the destructive risk unstated.

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

Conciseness3/5

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

The single sentence is front-loaded, unambiguous, and free of padding, so it is structurally sound. However, at this length it reads as under-specification rather than conciseness for a tool with four undocumented parameters and mutation semantics.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. Everything else is missing: for a destructive filesystem mutation with a sudo flag and an overwrite flag, the definition should at minimum describe the overwrite and privilege-escalation behavior and note that the source no longer exists afterward.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description must compensate and instead says nothing about source, destination, overwrite, or sudo. The two boolean flags in particular are ambiguous without documentation — overwrite's default-false replacement behavior and sudo's privilege escalation are entirely unexplained.

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 gives a specific verb and resource — 'Move/rename a file or directory' — which is distinctly a relocation operation, separable in intent from siblings like copy_path, delete_path, and get_path_info. It stops short of explicitly contrasting itself with copy_path for the move-vs-copy decision, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over copy_path + delete_path, no mention of prerequisites such as the destination existing or being writable, and no note about when the sudo escape hatch is warranted. The agent must infer all of this from the tool name alone.

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

Deploy Server

Other Tools