@wilsonbeam/openclaw-adb-mcp

Overview Schema Source Related Servers Discussions Admin

adb_pull_file

Copy a file from an Android device to your local machine using ADB. Specify the remote path on the device and the destination local path to transfer files directly.

Instructions

Pull a file from the Android device to local machine

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

Input Schema

Name	Required	Description
`deviceId`	No	Target device ID (optional)
`localPath`	Yes	Local file path
`remotePath`	Yes	Remote path on device

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 6, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the basic action, without disclosing behaviors like overwriting existing local files, handling of missing remote paths, or device connection requirements. Minimal transparency.

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?

The description is a single front-loaded sentence with no redundant words. It efficiently conveys the core purpose without any 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?

The tool is simple with three documented parameters and no output schema, but the description lacks behavioral context such as overwrite behavior or prerequisites. It is adequate as a bare minimum but not genuinely complete for an agent that needs to anticipate side effects.

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%, with all three parameters (deviceId, localPath, remotePath) described in the schema. The description adds no parameter information beyond what the schema already provides, so the baseline score of 3 applies.

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 states the verb 'Pull' and the resource 'file from the Android device to local machine', clearly indicating the direction and distinguishing it from adb_push_file. It is specific and unambiguous.

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 implies when to use this tool (device-to-local transfer) versus adb_push_file (local-to-device), but it does not explicitly state alternatives or exclusions. Usage is implied rather than clearly guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.