Skip to main content
Glama

adb_bugreport

Capture a full Android bug report zip containing device state, logs, dumpsys, and system info, and return the local file path for diagnostics.

Instructions

Capture a full bug report zip (device state, logs, dumpsys, system info). Returns the local file path.

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

Input Schema

NameRequiredDescriptionDefault
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

A3.5/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 usefully discloses that the artifact is written to a local file path rather than returned inline, but omits important behavior: bugreport capture is long-running (minutes), produces a large zip, may require specific permissions/root, and may affect device responsiveness. These omissions matter for a heavyweight operation.

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?

Two short sentences, zero filler, with the resource and its scope front-loaded and the return artifact stated second. Every clause earns its place.

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?

For a one-parameter tool with no output schema, the description covers what it produces and where it lands, which is adequate. However, given no annotations and the fact this is an expensive, long-duration capture, the absence of any runtime, size, or permission expectations leaves an agent underprepared to call it well.

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?

There is a single 'device' parameter with 100% schema description coverage, so the schema already documents it as a device serial. The description adds nothing about the parameter, such as whether omitting the optional device falls back to a default or single connected device. Baseline 3 applies when the schema 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?

States a specific verb ('Capture') and resource ('full bug report zip') and enumerates the contents (device state, logs, dumpsys, system info), which distinguishes it from point tools like adb_logcat or adb_dumpsys. It does not explicitly name those siblings as alternatives, so the differentiation is implied rather than stated.

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 word 'full' – an agent can infer this is the comprehensive diagnostic snapshot rather than a targeted log/dumpsys call. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must reason from the sibling list.

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