Skip to main content
Glama
Sign In
My MCP Server

My MCP Server

by Furkan-Keser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_file_or_folder

Moves a file or folder to a specified target directory within a restricted workspace.

Instructions

Dosya veya klasörü başka bir klasöre taşır.

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": {
      "path": "<path>",
      "target_directory": "<target_directory>"
    },
    "name": "move_file_or_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
target_directoryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

The description only states that the tool moves a file or folder, but does not disclose any side effects, permission requirements, or behavior on conflicts. No annotations provide additional context.

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 a single sentence that directly conveys the core action without unnecessary words, making it highly concise and front-loaded.

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?

Despite the simplicity of the operation, the description lacks critical context such as whether the move is synchronous, how conflicts are handled, and whether metadata is preserved. The output schema exists but does not compensate for this missing information.

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

Parameters2/5

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

With 0% schema description coverage, the description should explain the two parameters. It only implicitly suggests that target_directory is a folder, leaving path and target_directory semantics unclear.

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 verb 'move' and the resource 'file or folder', distinguishing it from sibling operations like copy, rename, and delete.

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?

No guidance on when to use this tool versus alternatives like rename_file_or_folder or copy_file_or_folder. The description does not mention scenarios or constraints.

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