DNS-DATA Remote

move_path

Destructive

Move or rename a remote file or directory on a registered, authorized online device. device_id identifies the target; source is the existing path and destination is the new path. overwrite defaults to false; when true it may replace existing data. Destructive if overwriting; confirm paths.

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": {
      "device_id": "<device_id>",
      "source": "<source>",
      "destination": "<destination>"
    },
    "name": "move_path"
  }
}

Input Schema

Name	Required	Description	Default
`source`	Yes
`device_id`	Yes
`overwrite`	No
`destination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotency. The description adds useful behavioral context: overwrite defaults to false, overwriting may replace existing data, and paths should be confirmed before use.

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 front-loaded with the core action, then explains target/path parameters and the overwrite warning in minimal sentences. Every sentence adds useful information without repetition.

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 destructive remote move/rename tool with no output schema, the description covers the target device, source/destination semantics, and overwrite risk. It could be slightly more complete by stating what happens when destination already exists and overwrite is false, but annotations already provide the safety profile.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It explains all four parameters: device_id identifies the target, source is the existing path, destination is the new path, and overwrite controls replacement behavior with a default of false.

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: move or rename a remote file or directory. It clearly distinguishes the operation from siblings like delete_path, read_file, or write_file by naming move/rename semantics.

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?

Implies the tool is used to move or rename paths on an authorized online device, and notes destructive risk when overwriting. However, it does not explicitly compare when to use this versus delete_path, write_file, or create_directory, nor does it state when-not to use it.

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

All DNS-DATA Remote 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?