Skip to main content
Glama
rahulkr
by rahulkr

pull_file

Transfer files from Android devices to your computer for development, testing, or debugging workflows. Specify remote and local paths to copy device files.

Instructions

Pull a file from the device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
remote_pathYes
local_pathYes
device_serialNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The pull_file tool handler, decorated with @mcp.tool() which serves as both the implementation and registration in the MCP framework. It executes the ADB 'pull' command to download a file from the Android device to local path.
    @mcp.tool()
    def pull_file(remote_path: str, local_path: str, device_serial: str | None = None) -> str:
        """Pull a file from the device"""
        return run_adb(["pull", remote_path, local_path], device_serial)
  • The @mcp.tool() decorator registers the pull_file function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('pull') which implies a read operation that copies a file, but doesn't mention permissions needed, whether it overwrites local files, error handling, or performance aspects like file size limits. This leaves significant gaps for a tool that interacts with device storage.

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, clear sentence with zero wasted words. It's appropriately sized for a basic tool description and front-loads the core action. Every word earns its place by conveying the essential purpose.

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?

Given the tool has an output schema (which handles return values), no annotations, and simple parameters, the description is minimally complete but lacks important context. It covers the basic 'what' but misses 'how' details like parameter usage, behavioral traits, and differentiation from siblings, making it adequate but with clear gaps for practical use.

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 compensate for three undocumented parameters. The description mentions 'from the device' which hints at the 'device_serial' parameter, but doesn't explain 'remote_path' (what path format, what locations are accessible) or 'local_path' (where files are saved, path requirements). It adds minimal value beyond the parameter names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Pull a file from the device' clearly states the action (pull) and resource (file), but it's vague about scope and doesn't differentiate from sibling tools like 'pull_recordings' or 'read_file'. It specifies the source as 'the device', which provides some context but lacks detail on what types of files or from where on the device.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'pull_recordings' (for recordings), 'read_file' (for reading without pulling), or 'list_files' (for listing). The description implies file retrieval but doesn't specify prerequisites, constraints, or comparison to other file-related tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rahulkr/r_adb_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server