Skip to main content
Glama

adb_grep

Search file contents on Android devices by text pattern using fixed-string or regex matching. Supports recursive search, depth control, and result capping.

Instructions

Search file contents on the device by text pattern. Uses fixed-string matching by default (no regex injection risk). Supports recursive directory search with depth control and result capping. For filename searches, use adb_find instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternYesText pattern to search for
pathYesFile or directory path to search
recursiveNoSearch directories recursively
fixedStringNoUse fixed-string matching (default: true, safer). Set false for regex.
ignoreCaseNoCase-insensitive search (default: true)
maxResultsNoMaximum matching lines to return (1-10000, default 500)
maxDepthNoMaximum directory depth for recursive search (1-50, default 10)
filesWithMatchesNoShow only filenames that contain matches, not the matching lines
rootNoUse root shell for protected paths
deviceNoDevice serial
Behavior4/5

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

With no annotations, description carries full burden. It discloses safety features (fixed-string default, no regex injection), recursion, depth control, and result capping. Lacks specifics on output format or error handling, but covers key behavioral traits.

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 with front-loaded purpose, no fluff. Every sentence adds value: purpose, safety, capabilities, and sibling alternative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters and no output schema, description covers core purpose, defaults, safety, and alternatives. Could detail output format or root option, but sufficient for agent decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers parameters 100% with descriptions. The description adds meaning by explaining default fixed-string matching, recursive search with depth control, and result capping, improving context beyond schema.

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 file contents by text pattern, using specific verbs and resources. It distinguishes from sibling tool adb_find for filename searches.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool (text pattern search) and when not (for filename searches, use adb_find). Also mentions default behavior and capabilities like recursive search and result capping.

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