Skip to main content
Glama

adb_logcat

Capture Android logcat snapshots with tag, priority, buffer, and grep filters to isolate relevant device logs for debugging.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adb_logcat"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / result_handle
      Added value: +{
      +  "description": "Optional. 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.",
      +  "maxLength": 32,
      +  "minLength": 1,
      +  "pattern": "^[a-zA-Z0-9_-]+$",
      +  "type": "string"
      +}
    • addedInput schema / properties / result_handle_ttl
      Added value: +{
      +  "description": "Optional. TTL in seconds for the result handle (60 to 604800). Default 43200 (12 hours). Ignored if result_handle is not provided.",
      +  "maximum": 604800,
      +  "minimum": 60,
      +  "type": "integer"
      +}
  3. First observedv1.1.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does not say this is a read-only, non-destructive operation, does not mention device-selection or permission requirements, and says nothing about what the capture returns. The only behavior-ish hint is the implied snapshot semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core action front-loaded and no filler. The second sentence mildly duplicates the schema, keeping it from a 5.

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 an 8-parameter tool with no annotations and no output schema, the description omits too much: neither the shape of the returned data (raw log lines vs. structured entries) nor the combined-filter behavior nor the effect of result_handle/ttl handles is explained. An agent can call it, but must infer return format and filtering interactions.

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 every parameter (tag, grep, lines, buffer, device, priority, result_handle, ttl) is already documented in the schema. The description's mentions of tag, priority, and grep simply restate a subset of that, adding no syntax, defaults, or interaction semantics beyond the schema. Baseline 3 applies.

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?

"Capture a logcat snapshot" gives a specific verb and resource, and the second sentence names the supported filtering dimensions. It is clear what the tool does, but it never distinguishes itself from siblings like adb_logcat_start, adb_logcat_poll, adb_logcat_crash, or adb_logcat_clear, all of which also surface log data.

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 word "snapshot" implies a one-shot capture rather than a streaming session, which hints at when to prefer this over adb_logcat_start/adb_logcat_poll. However, that contrast is never stated, and there are no explicit when-to-use, when-not-to-use, or alternative-tool instructions despite a dense logcat sibling cluster.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools