Bot-Hosting.net

Duplicate a file

files_copy

Destructive

Duplicate a file in place (the node appends a " copy" suffix). NOT a move: to move or rename, use files.rename.

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": {
      "id": "<id>",
      "location": "<location>"
    },
    "name": "files_copy"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`location`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing the automatic " copy" suffix, which is real behavioral information an agent cannot get from the schema. With destructiveHint=true and idempotentHint=false already declared, it could still say what happens when a file named with that suffix already exists (overwrite vs. further suffixing), which is the main open question for a destructive tool.

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 sentences with zero filler; the primary behavior and its observable side effect come first, and the disambiguation follows. Every clause carries information an agent needs.

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

Completeness3/5

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

The safety profile is covered by annotations and there is no output schema to explain, so the remaining burden is modest. However, for a destructive, non-idempotent mutation with two undocumented parameters, the description should clarify where the copy lands and how collisions are handled before an agent can call it confidently.

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?

Schema description coverage is 0%, so the description carries the full burden, yet it never explains the parameters. It is unclear whether "location" is the destination directory for the duplicate or something else, nor whether the " copy" suffix applies to id (the filename) and how it interacts with location.

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?

States a specific verb and resource ("Duplicate a file") and immediately scopes it with "in place" plus the concrete outcome that the node appends a " copy" suffix. It explicitly negates the confusing sibling concept (move) so an agent can distinguish copy from move/rename without opening any 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 explicit when-not guidance ("NOT a move") and routes to a named alternative, files.rename, for move/rename needs. Minor gap: the sibling catalog also contains files_move, so naming only files.rename as the destination for "move" is slightly incomplete, and there is no guidance on when to copy versus download/upload.

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

All Bot-Hosting.net tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?