Skip to main content
Glama

adb_file_copy

Copy files or directories between Android device paths, checking free space before and verifying copied size after; enable recursive mode for directories.

Instructions

Copy a file or directory on the device. Pre-flight checks source size against destination available space. Post-verifies the copy by comparing file sizes. For recursive directory copies, use -r flag.

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_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoUse root shell for protected paths
deviceNoDevice serial
sourceYesSource file or directory path
recursiveNoCopy directories recursively (-r)
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

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden, and it does disclose two non-obvious traits: a pre-flight free-space check and a post-copy size verification. It still omits critical mutation semantics — whether an existing destination is overwritten, what happens to a partial copy on failure, and whether verification failure raises an error or merely reports it.

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?

Three short sentences, front-loaded with the core action, then the safety behaviors, then the recursive note. The final sentence is largely redundant with the `recursive` schema property, but overall there is little 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 mutation tool with no annotations and no output schema, the description should say more about results and failure modes — particularly since it advertises post-copy verification whose outcome an agent would need to interpret. Overwrite behavior and the shape of the verification result are the notable gaps.

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 all five parameters (including `root` for protected paths and `recursive`) are already documented in the schema. The description only echoes the `-r` mapping for recursion and adds no meaning beyond that, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ('Copy a file or directory on the device') and mentions recursive directory handling. However, in a sibling set containing adb_push, adb_pull, and adb_file_move, it never states how this on-device copy differs from those, leaving the agent to infer the distinction.

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

Usage Guidelines2/5

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

The only usage-like statement is 'For recursive directory copies, use -r flag,' which merely restates the `recursive` parameter. There is no guidance on when to prefer this over adb_push (host-to-device), adb_pull, or adb_file_move, and no stated preconditions such as root requirements for protected paths.

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