Skip to main content
Glama
Sign In
My MCP Server

My MCP Server

by Furkan-Keser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

copy_file_or_folder

Copies a file or folder to a specified target directory within a secure workspace.

Instructions

Dosya veya klasörü güvenli çalışma alanında kopyalar.

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": "copy_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

C2.4/5.0
Behavior2/5

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

Without annotations, the description must disclose behavioral traits. It mentions 'güvenli çalışma alanında' (in safe workspace) but omits details like overwrite behavior, recursion, or error conditions.

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 description is a single sentence, concise but excessively brief given the lack of schema descriptions. It could be expanded without losing conciseness.

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?

The tool has an output schema but it is not described. Essential context like what happens on conflict, directory recursion, and required permissions is missing, making the description incomplete for a copy operation.

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%, and the description adds no information about the parameters 'path' or 'target_directory', leaving their meanings and constraints undefined.

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 clearly states the action (copy) and resource (file or folder) in Turkish. It distinguishes from siblings like move and rename, but lacks specificity about scope or conditions.

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 copy vs. alternatives like move_file_or_folder. The description does not provide usage context or exclusions.

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