Skip to main content
Glama
Sign In
android-device-mcp

android-device-mcp

by prashant1507
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Copy File to Device

push_file

Copy files from your computer to an Android device by specifying the device serial, local file path, and destination folder on the device.

Instructions

Push or copy files from a given directory on local machine to an Android device using its serial number.

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": {
      "serial": "<serial>",
      "local_file": "<local_file>",
      "folder_path_in_device": "<folder_path_in_device>"
    },
    "name": "push_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYes
local_fileYes
folder_path_in_deviceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It states the action but omits critical details: whether it overwrites existing files, handles directories recursively, requires specific permissions, or what happens on failure (e.g., file not found, invalid path).

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?

The description is a single, concise sentence that covers the core purpose efficiently. It is front-loaded and easily parsed, but could be slightly more structured (e.g., breaking out prerequisites) without harming conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that modifies device storage with no output schema and no annotations, the description lacks completeness. It fails to mention return values (e.g., success indicator), error handling, or behavior for directories vs. files, leaving gaps for an agent.

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

Parameters2/5

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

Schema coverage is 0%, so the description should compensate. It adds context for 'serial' (using serial number) and 'local_file' (from local directory), but 'folder_path_in_device' remains vague. No format hints (absolute/relative), constraints, or mutual dependencies are provided.

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?

The description clearly states the action ('push or copy'), source ('local machine'), destination ('Android device using its serial number'), and specific intent. It effectively distinguishes from sibling tools like pull_file, which does the reverse.

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 description implies usage for transferring files to a device but provides no explicit guidance on when to use it versus alternatives like install_app or pull_file. No prerequisites (e.g., device connected, adb available) or exclusions are mentioned.

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