Skip to main content
Glama

Push Adb File

push_adb_file
Destructive

Transfers a local file to an absolute path on an Android device over ADB, refusing to replace existing files unless overwrite is enabled and verifying the transfer with a SHA-256 digest if available.

Instructions

Push one local file to an absolute device path. The only device-mutating ADB tool: existing device files are refused unless overwrite is explicitly requested, and the transfer is verified by comparing the local digest with the device's own sha256sum when the device provides one.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serial": "emulator-5554",
      "local_path": "/tmp/frida-server",
      "device_path": "/data/local/tmp/frida-server"
    },
    "name": "push_adb_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesDevice serial exactly as `adb devices` reports it
overwriteNoAllow replacing an existing device file; refused by default
local_pathYesExisting local regular file to push
device_pathYesAbsolute destination path on the device

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already carry destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is known; the description adds real value beyond that by disclosing the overwrite refusal default and a sha256sum digest verification step with its caveat ('when the device provides one'). It still omits what happens on verification mismatch or partial transfer.

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?

Two tight sentences with the action stated first and the constraints following; every clause (refusal default, digest verification) carries substantive information and nothing is padded.

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, open-world mutation with no output schema, the definition covers the essential risks: existing files protected, transfer verified. A note on failure behavior or the returned result would fully close the loop, but an agent has enough to invoke it correctly.

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% and the schema already documents serial, local_path, device_path and the overwrite default, so the description only reinforces the overwrite refusal semantics. Baseline 3 is appropriate since the schema does the heavy lifting.

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 concrete verb and resource ('Push one local file to an absolute device path') and explicitly positions it against siblings by declaring it 'the only device-mutating ADB tool', which separates it from the pull/read-heavy family without naming them.

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

Usage Guidelines4/5

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

Gives clear contextual guidance — this is the sole device-mutating ADB operation — plus the key usage constraint that existing device files are refused unless overwrite is requested. It does not spell out error/retry or prerequisite conditions (e.g. root-only paths), but the direction of use is unambiguous.

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