Skip to main content
Glama

stop_logcat_capture

Stop a running logcat capture on an Android device and return the collected logs, filtered by priority, tag, or substring, with a configurable tail limit to avoid token overflow.

Instructions

Stop the running logcat capture and return what was collected since start, optionally filtered by a case-insensitive substring, a minimum priority (V/D/I/W/E/F), and/or tags (OR'd). Output is capped to the last 500 lines by default (override with tail) so a long capture doesn't blow the token budget — narrow with the filters first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoKeep only lines whose log tag contains one of these (case-insensitive, OR'd).
tailNoKeep only the last N lines after filtering (the most recent, where a crash usually is). Default 500; pass a larger number for more, or a huge one to effectively disable the cap.
filterNoCase-insensitive substring to keep.
redactNoMask common secrets (token, password, authorization, api key, secret) before returning captured lines.
serialNoTarget device serial (adb -s). Optional when exactly one device is attached.
priorityNoMinimum priority to keep: V, D, I, W, E, or F.
Behavior3/5

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

No annotations exist, so the description carries full burden. It discloses output capping (500 lines default, tail override), filtering behavior (case-insensitive, OR'd tags, priority levels), and redaction of secrets. However, it does not explain what happens if no capture is running, error handling, or the exact return format.

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, well-structured sentence that front-loads the core purpose and then efficiently enumerates filtering options, output capping, and best practice advice. Every clause adds value without redundancy.

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?

The tool has no output schema, so the description must clarify the return. It mentions 'lines' but not whether output is a string or array, and does not detail the lifecycle with start_logcat_capture. Sibling relationships are not addressed. The description is sufficient for basic use but leaves gaps in full operational context.

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?

Schema coverage is 100%, baseline 3. The description adds meaningful context: explains tail's utility for crash debugging, lists priority letters, specifies redacted secrets, clarifies serial's optionality, and describes tag matching as OR'd. This exceeds the schema's own descriptions.

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 stops a running logcat capture and returns collected output, with options for filters. It distinguishes from siblings like start_logcat_capture and logcat by specifying the 'stop and collect' action.

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 after a call to start_logcat_capture but does not explicitly state prerequisites or when not to use. It offers a tip to narrow filters first, but lacks a clear context of lifecycle 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/iksnerd/adb-mcp'

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