Skip to main content
Glama

adb_crash_logs

Retrieve recent ANR traces and tombstone crash dumps from an Android device to diagnose app hangs and native crashes. Root access is required for /data/anr/ and /data/tombstones/.

Instructions

Read ANR (Application Not Responding) traces and tombstone crash dumps from the device. Requires root access for /data/anr/ and /data/tombstones/. Returns the most recent entries.

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_crash_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoType of crash data to retrieve (default: both)both
deviceNoDevice serial
maxEntriesNoMaximum entries to return per type (1-20, default 5)

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. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the root prerequisite and the paths read, plus that only the most recent entries are returned. It does not say whether the tool attempts to acquire root itself, how it fails on an unrooted device, or the format of the returned traces — meaningful gaps for an unannotated tool.

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 short sentences, each earning its place: what is read, the root prerequisite, and the recency/shape of the result. Front-loaded with the resource and free of filler.

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?

For a 3-parameter read tool with no output schema and no annotations, the description covers the essentials: data source, permission requirement, and result recency. The remaining gap — failure behavior without root and the structure of returned trace text — is modest but real.

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% and the enum on "type" plus the maxEntries bounds are already fully documented in the schema. The description's phrase "most recent entries" loosely reinforces maxEntries but adds no syntax, format, or per-type behavior beyond what the schema states.

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?

Uses a specific verb ("Read") with two concrete resources (ANR traces and tombstone crash dumps) and even expands the ANR acronym, so the agent knows exactly what data this yields. It does not, however, differentiate itself from nearby siblings such as adb_logcat_crash, adb_bugreport, or adb_dumpsys, which an agent could reasonably confuse it with.

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?

Usage is only implied by the resource type: reach for this when diagnosing ANRs or native crashes. The description states a hard prerequisite (root access for /data/anr/ and /data/tombstones/), which is genuinely useful context, but it never says when to prefer this over adb_logcat_crash or adb_bugreport, nor what to do if the device is not rooted.

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