Skip to main content
Glama

adb_logcat

Capture Android logcat snapshots with filtering by tag, priority, and grep pattern for efficient debugging.

Instructions

Capture a logcat snapshot. Supports tag filtering, priority levels, and grep patterns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesNoNumber of recent lines to capture (1-10000)
tagNoFilter by tag (e.g., 'ActivityManager' or 'MyApp')
priorityNoMinimum priority: V(erbose), D(ebug), I(nfo), W(arn), E(rror), F(atal)
grepNoGrep filter applied to output (literal string match, case-insensitive)
deviceNoDevice serial
bufferNoLogcat buffer to read frommain
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.
Behavior2/5

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

No annotations provided, so description bears full burden. It mentions filtering but does not disclose side effects (e.g., buffer consumption, impact on other sessions) or safety 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?

Single sentence, front-loaded with the core action, no wasted words. Efficient and clear.

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?

For a tool with 8 parameters and no output schema, the description is too minimal. It omits return format, details on buffer/device parameters, and the result_handle mechanism, leaving significant gaps.

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 baseline is 3. The tool description summarizes three filter types (tag, priority, grep) but adds no meaning beyond schema to lines, device, buffer, or the complex result_handle mechanism.

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

Purpose4/5

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

The description clearly states it captures a logcat snapshot with tag, priority, and grep filtering. The word 'snapshot' implies one-time capture, but it doesn't explicitly differentiate from continuous logcat tools like adb_logcat_poll or adb_logcat_start/stop.

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 on when to use this tool versus siblings like adb_logcat_poll (streaming), adb_logcat_start/stop (session), or adb_logcat_clear (clearing). Lacks exclusions or alternatives.

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