Skip to main content
Glama

adb_file_move

Move or rename files or directories on an Android device via ADB; use root for protected paths and expect copy+delete behavior across filesystems.

Instructions

Move or rename a file/directory on the device. Moving FROM a system path is destructive — source depth protection refuses if source is at depth ≤ 1 from root. Symlinks resolved before checks. Cross-filesystem moves (e.g., /data → /sdcard) do a copy+delete internally and can be slow for large files.

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

Input Schema

NameRequiredDescriptionDefault
rootNoUse root shell for protected paths
deviceNoDevice serial
sourceYesSource file or directory path
destinationYesDestination path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it flags destructiveness, the source-depth protection rule (depth ≤ 1 from root), pre-check symlink resolution, and the copy+delete fallback with a performance warning for cross-filesystem moves. It still omits whether an existing destination is overwritten and whether root is required for protected paths.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences, front-loaded with the core action, and each subsequent sentence adds a distinct hazard or behavior. Slight density in the depth-protection clause costs it the top mark, but there is no filler.

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 mutation tool with no annotations and no output schema, the description covers the important failure and performance characteristics an agent needs before calling it. The remaining gaps — destination overwrite semantics and explicit root prerequisite — are minor but real.

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 coverage is 100%, so source, destination, device and root are already documented, and the baseline is 3. The description adds indirect meaning (system paths tie to the root flag, symlink resolution affects how source is interpreted), but it never explicitly explains the root or device parameters.

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 pair (move/rename) and resource (file/directory on the device), which cleanly separates it from sibling tools like adb_file_copy, adb_rm, adb_push and adb_pull. The rename capability is called out explicitly, so an agent knows this is not just a path-to-path transfer.

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?

Usage is implied rather than stated: an agent infers 'use this to relocate or rename a path' but no alternative is named and no explicit when-not guidance is given. The source-depth refusal rule is operation-time behavior, not selection guidance, though it does hint at when the call will fail.

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