Nodecraft

Copy File or Folder

copy_path

Destructive

Copy a file or folder on a specific instance (by id or exact name). Useful for taking a quick backup of a config file before editing it. Copying is additive and needs no confirmation, unless overwrite is set, which destroys whatever is already at the destination and requires confirm: true.

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": {
      "instance": "<instance>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "copy_path"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Destination, from the instance root.
`from`	Yes	File or folder to copy, from the instance root.
`confirm`	No	Required only when `overwrite` is true. Show the user what will be replaced before setting this.
`instance`	Yes	Instance id (preferred) or exact instance name.
`overwrite`	No	Allow replacing an existing file at `to`. Anything already there is lost, so this also requires `confirm`.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes beyond the blanket destructiveHint=true annotation by explaining that the default copy is additive and needs no confirmation, and that destruction only occurs when `overwrite` is set, at which point `confirm: true` is required. This narrows a coarse annotation into an accurate conditional safety model, which is exactly the context an agent needs before mutating a filesystem.

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?

Three short sentences, front-loaded with identity and scope, then use case, then the destructive conditional. No filler or repeated information.

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 five-parameter copy operation with no output schema, the definition covers identity, safety, and confirmation requirements completely. The only small gap is that it does not say what happens on name collisions when `overwrite` is false or what the call returns on success.

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 description coverage is 100%, so the schema already documents `instance`, `from`, `to`, `overwrite`, and `confirm`. The description restates the overwrite/confirm dependency in prose but adds no format, path-syntax, or edge-case detail beyond what the schema already supplies. Baseline 3 is appropriate.

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 and resource ('Copy a file or folder') plus the scoping detail that the instance is identified by id or exact name. It does not explicitly differentiate itself from move_path or create_backup, but the copy semantics are unambiguous enough that an agent can select it without opening the schema.

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

Usage Guidelines4/5

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

Gives a concrete usage scenario ('taking a quick backup of a config file before editing it') that tells the agent when this tool is a good fit. It stops short of naming alternatives such as move_path or create_backup, or stating when copying is the wrong choice.

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

All Nodecraft tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?