Skip to main content
Glama

adb_find

Search for files on an Android device using glob patterns. Supports filtering by type, depth, and result limits to prevent excessive output.

Instructions

Search for files on the device by name or pattern. Uses the find command with glob matching. Results are capped at maxResults to prevent unbounded output. Reports whether results were truncated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchPathNoStarting directory for search/sdcard
nameYesFilename pattern (glob: *.apk, config.*, *test*)
typeNoFilter by type: file, directory, or anyany
maxDepthNoMaximum directory depth to search (1-50, default 10)
maxResultsNoMaximum results to return (1-10000, default 500)
rootNoUse root shell for system paths
deviceNoDevice serial
result_handleNoOptional. If provided, store this tool's result under `result://<tool>/<name>` for retrieval after compaction. Name must be 1-32 chars, [a-zA-Z0-9_-]. Existing handles with the same tool+name are overwritten. Use adb_result_list to see active handles, adb_result_get or the MCP Resource URI to retrieve.
result_handle_ttlNoOptional. TTL in seconds for the result handle (60 to 604800). Default 43200 (12 hours). Ignored if result_handle is not provided.
Behavior4/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 discloses result capping and truncation reporting, which are useful behavioral traits. However, it does not cover error handling, performance implications, or permissions for root searches, which are relevant given the root parameter.

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?

Three sentences, each serving a purpose: purpose, method, and behavior. Front-loaded with core purpose. No wasted words.

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?

With no output schema, the description should specify the return format (e.g., list of absolute paths). It only mentions truncated reporting, leaving the exact return structure unclear. Also lacks information on error handling or performance warnings. Incomplete for a tool with 9 parameters and no output schema.

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?

Parameter schema coverage is 100%, and the schema descriptions are detailed. The description adds only that name uses glob patterns and results are capped, which is already partially covered by schema defaults and descriptions. Thus, minimal added value beyond schema, baseline of 3.

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 tool searches for files by name/pattern using glob matching, which is a specific verb+resource. It distinguishes from siblings like adb_grep (content search) and adb_ls (directory listing) by focusing on file name pattern matching.

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 file name searches but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. The context is clear but lacks exclusion criteria.

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/fullread/DeepADB'

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