Skip to main content
Glama

adb_logcat

Capture a logcat snapshot from Android devices with tag, priority, grep, and buffer filters for precise diagnostics.

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
Behavior2/5

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

No annotations exist, so the description must carry behavioral context. It implies a non-destructive read but does not disclose that the output is raw log lines, that the log is not cleared, or other behaviors like device handling.

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, efficient sentence that front-loads the primary action and key features. No redundant information.

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?

No output schema exists, but the description does not specify what the tool returns (e.g., log lines). With complex filtering options and many logcat sibling tools, the description lacks sufficient completeness for correct agent invocation.

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 documents all parameters. The description adds no extra semantics beyond grouping a few filter types, which is already clear from the schema.

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 the action ('Capture a logcat snapshot') and the resource, and mentions supported filtering options. It distinguishes from siblings like adb_logcat_poll by implying a one-time snapshot, but does not explicitly differentiate.

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 vs. alternatives like adb_logcat_poll or adb_logcat_start. Given the many logcat sibling tools, this omission reduces usability.

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