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

android-device-mcp

by prashant1507
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Copy Files from Device

pull_file

Copy files from an Android device directory to a local folder by providing the device serial number and file path.

Instructions

Pull or copy files from a given directory on 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>",
      "file_path_in_device": "<file_path_in_device>"
    },
    "name": "pull_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYes
file_path_in_deviceYes
local_folderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only describes the action but doesn't mention important aspects like overwrite behavior, error handling, permission requirements, or whether it supports directories. This is insufficient for a file operation tool.

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

Conciseness3/5

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

The description is a single sentence that is concise but lacks structure. It could benefit from being broken into clearer statements or bullets to improve readability without adding length.

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?

Given three parameters and no output schema, the description should specify what the tool returns, error scenarios, and constraints (e.g., file vs directory). It only mentions the basic action, leaving the agent unclear about behavior and results.

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 description coverage is 0%, so the description must add meaning to parameters. It mentions 'directory' and 'serial number' but does not explain the parameters (serial, file_path_in_device, local_folder) in detail. The relationship between 'directory' and file_path_in_device is ambiguous, and the optional local_folder is not described.

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 verb (copy/pull), the resource (files from a directory on an Android device), and the required identifier (serial number). It distinguishes from sibling tools like push_file and list_files.

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 copying files from a device but provides no explicit guidance on when to use this tool versus alternatives (e.g., taking a screenshot or dumping screen). No exclusions or alternatives 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