whatbox-mcp

Overview Schema Source Related Servers Discussions Admin

Move a Whatbox Path

whatbox_move_path

Move or rename files or folders between allowed roots on Whatbox while preventing accidental overwrites. Changes are reversible for safety.

Instructions

Move or rename a path between allowed roots without overwriting an existing destination. Reversible.

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": {
      "sourceRelativePath": "<sourceRelativePath>",
      "destinationRelativePath": "<destinationRelativePath>"
    },
    "name": "whatbox_move_path"
  }
}

Input Schema

Name	Required	Description	Default
`sourceRootIndex`	No
`sourceRelativePath`	Yes
`destinationRootIndex`	No
`destinationRelativePath`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.0Aug 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already indicate a mutating, non-destructive operation. The description adds valuable context with 'without overwriting an existing destination' and 'Reversible,' clarifying safety guarantees beyond the boolean hints. It does not mention permissions or failure modes, but the added detail is meaningful.

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 two sentences and front-loads the primary verb and object. The second sentence 'Reversible' is brief but adds a useful behavioral note without waste.

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?

For a 4-parameter tool with no output schema and no informative annotations, the description provides the core action and constraints but omits details about parameter semantics and return behavior. 'Allowed roots' and 'Reversible' are not elaborated, leaving some ambiguity, but the tool's simplicity keeps it minimally viable.

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 must explain the parameters, but it does not. It mentions 'roots' but does not introduce sourceRootIndex or destinationRootIndex, nor does it clarify that paths are relative strings. The agent is left without guidance on populating the required fields.

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 uses the specific verbs 'Move or rename' and identifies the resource as 'a path between allowed roots,' clearly distinguishing it from sibling tools like upload, download, or quarantine. The title 'Move a Whatbox Path' reinforces the function without ambiguity.

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

Usage Guidelines3/5

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

The description implies the tool is for moving or renaming files but does not explicitly state when to use it over alternatives such as whatbox_upload_path or whatbox_download_path. No exclusions or alternative tool references are provided, so usage context is only implied.

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