Skip to main content
Glama

adb_logcat_crash

Get recent crash logs from the crash buffer

Instructions

Get recent crash logs from the crash buffer

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

Input Schema

NameRequiredDescriptionDefault
linesNoNumber of lines (1-10000)
deviceNoDevice serial

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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the entire burden. It does signal that results are 'recent' (implying a bounded window rather than full history) and scoped to the crash buffer specifically, which is useful. But it says nothing about read-only safety, the default of 50 lines, the maximum of 10000, the behavior when no device is specified, or the 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.

Conciseness4/5

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

A single front-loaded sentence with no filler. It's efficient, though it may be too sparse to earn its place as the sole guidance for an agent choosing among several log tools.

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?

The tool itself is simple (2 optional params, no output schema, no annotations), so not much is required. Still, the description leaves the key decision of 'crash buffer vs. crash_logs vs. logcat' unresolved and never mentions the default device handling or default line count. For a tool in a large family of log/crash siblings, that gap matters.

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 both 'lines' (1-10000, default 50) and 'device' (serial) are fully documented in the schema. The description adds no syntax or semantics beyond that. The baseline 3 is appropriate since the schema already does the work.

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 gives a specific verb and resource: 'Get recent crash logs from the crash buffer'. It's clear what it retrieves and that it targets the dedicated crash buffer. However, it doesn't distinguish this tool from its close siblings 'adb_crash_logs' or the general 'adb_logcat' family, which an agent would need to choose between.

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?

There's no indication of when to use this tool versus 'adb_crash_logs' or 'adb_logcat', or when not to. No prerequisites, no alternates mentioned. The agent has to infer selection from names alone.

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