Skip to main content
Glama

adb_push

Push a local file to an Android device's filesystem after checking blocked kernel paths, filesystem warnings, symlink resolution, and destination storage availability.

Instructions

Push a local file to the device filesystem. Pre-flight checks: hard-blocked kernel paths, filesystem type warnings, symlink resolution, and destination storage availability.

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": {
      "localPath": "<localPath>",
      "remotePath": "<remotePath>"
    },
    "name": "adb_push"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
localPathYesLocal file path to push
remotePathYesDestination path on device

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.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden, and it does disclose real behavior: kernel paths are hard-blocked, filesystem type issues produce warnings, symlinks are resolved, and destination storage is checked. It does not say whether an existing destination file is overwritten, whether a failed pre-flight aborts the push or merely warns, or what permissions are needed, leaving gaps for a mutation tool.

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?

Two sentences, front-loaded with the core action, and the pre-flight list is compact and information-dense. The second sentence is a fragment list rather than prose, which is acceptable but slightly telegraphic.

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 file-mutating tool with no annotations and no output schema, the description covers pre-flight validation well but omits overwrite semantics, failure behavior, and permission requirements. Those omissions are material for an agent deciding whether calling it is safe.

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 the schema already documents localPath, remotePath, and device; the description adds only an indirect hint that remotePath is validated for storage availability and kernel-path blocking. Baseline 3 is appropriate given the schema does the heavy lifting.

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?

States a specific verb (push) plus the direction and resource (local file to device filesystem), which cleanly separates it from adb_pull, adb_file_write, and adb_file_copy without naming them. It stops short of explicitly naming the reverse-direction sibling, so it is a strong but not exemplary 5.

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 direction of transfer implies when to use it, and the pre-flight note hints it is the safe path for file deployment. However, it never states prerequisites (adb root, remount for system partitions) or explicitly contrasts with adb_file_write or adb_pull, so the agent must infer them.

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