Skip to main content
Glama

Pull Adb File

pull_adb_file

Pull an absolute device file path via ADB into a selected local directory, compute its SHA-256 digest, and prevent overwriting existing copies; device access remains read-only.

Instructions

Pull one absolute device path (a database, shared-preferences XML, or any readable file) into a caller-selected output directory, digesting it with SHA-256. The local copy must not already exist. Read-only with respect to the device.

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",
      "device_path": "/data/data/com.example.app/databases/app.db",
      "output_directory": "/tmp/rea-pulls"
    },
    "name": "pull_adb_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesDevice serial exactly as `adb devices` reports it
device_pathYesAbsolute device filesystem path to pull
output_directoryYesLocal directory for the pulled file; must not already contain the file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, and the description usefully resolves the apparent tension by scoping the read-only claim to the device while the local filesystem is written. It also discloses the SHA-256 digest step and the no-pre-existing-copy constraint, though it says nothing about failure modes or verification.

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 sentences, front-loaded with the action and its scope, then the constraints. No filler and nothing buried.

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?

There is no output schema, so the description carries the burden of explaining what an agent gets back; it only gestures at a SHA-256 digest without stating the return shape (local path, hash, success indicator). For a three-parameter file-transfer tool with a precondition that can fail, that is a real gap.

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%, so the schema already defines serial, device_path and output_directory. The description reinforces 'absolute device path' and 'file must not already exist' but adds no format, syntax, or naming detail beyond what the schema documents.

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 a concrete verb and resource ('Pull one absolute device path') plus concrete file-type examples (database, shared-preferences XML, any readable file) and the destination ('caller-selected output directory'), which cleanly separates it from the push-side sibling without naming it.

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?

It gives one hard precondition ('The local copy must not already exist') but never says when to prefer this over pull_adb_package or when to use list_adb_directory first. Usage is implied by the scope statement rather than routed explicitly.

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