Skip to main content
Glama
Neem2004

Android ADB MCP Server

by Neem2004
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

adb_get_logcat

Captures Android logcat output by dumping the buffer for debugging. Filter results by tag, minimum log level, and last N lines.

Instructions

Dumps and exits the Android logcat buffer (logcat -d; not a stream), returning newline-separated lines with blank lines removed. Optionally filters by tag, minimum log level and the last N lines. Use filter_tag alone for 'tag:'; log_level only takes effect together with filter_tag. / Vuelca y cierra el buffer de logcat del dispositivo (logcat -d; no es un stream), devolviendo líneas separadas por saltos de línea y omitiendo las vacías. Filtra opcionalmente por tag, nivel mínimo de log y las últimas N líneas. filter_tag solo produce 'tag:'; log_level solo tiene efecto junto con filter_tag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesNoNumber of last lines to return (defaults to the full buffer). / Número de últimas líneas a retornar (por defecto, el buffer completo).
log_levelNoMinimum log level to include (V=verbose … F=fatal). Requires filter_tag to take effect; ignored otherwise. / Nivel mínimo de log a incluir (V=verbose … F=fatal). Requiere filter_tag para tener efecto; se ignora si no va.
filter_tagNoOnly include entries whose tag matches this log tag (e.g. MyApp). / Incluye solo entradas cuyo tag coincida (p. ej. MyApp).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.2
    • addedInput schema / properties / filter_tag / title
      Added value: +"filter_tag"
    • addedInput schema / properties / lines / maximum
      Added value: +1000
    • addedInput schema / properties / lines / title
      Added value: +"lines"
    • changedInput schema / properties / log_level / description
      Previous value: -"Minimum log level to include (V=verbose … F=fatal). Requires filter_tag to take effect. / Nivel mínimo de log a incluir (V=verbose … F=fatal). Requiere filter_tag para tener efecto."New value: +"Minimum log level to include (V=verbose … F=fatal). Requires filter_tag to take effect; ignored otherwise. / Nivel mínimo de log a incluir (V=verbose … F=fatal). Requiere filter_tag para tener efecto; se ignora si no va."
    • addedInput schema / properties / log_level / title
      Added value: +"log_level"
  2. Changed8 schema fields changedv1.0.1
    • changedInput schema / properties / filter_tag / description
      Previous value: -"Filtra entradas por tag (etiqueta de log)."New value: +"Only include entries whose tag matches this log tag (e.g. MyApp). / Incluye solo entradas cuyo tag coincida (p. ej. MyApp)."
    • addedInput schema / properties / filter_tag / examples
      Added value: +[
+  "MyApp",
+  "ActivityManager"
+]
    • addedInput schema / properties / lines / default
      Added value: +200
    • changedInput schema / properties / lines / description
      Previous value: -"Número de últimas líneas a retornar."New value: +"Number of last lines to return (defaults to the full buffer). / Número de últimas líneas a retornar (por defecto, el buffer completo)."
    • addedInput schema / properties / lines / examples
      Added value: +[
+  200,
+  1000
+]
    • addedInput schema / properties / lines / minimum
      Added value: +1
    • changedInput schema / properties / log_level / description
      Previous value: -"Nivel mínimo de log a incluir."New value: +"Minimum log level to include (V=verbose … F=fatal). Requires filter_tag to take effect. / Nivel mínimo de log a incluir (V=verbose … F=fatal). Requiere filter_tag para tener efecto."
    • addedInput schema / properties / log_level / examples
      Added value: +[
+  "D",
+  "E"
+]
  3. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does well: it discloses that the command exits rather than streams, returns newline-separated lines with blanks removed, defaults to the full buffer, and notes the log_level/filter_tag dependency. It omits auth/device-connection prerequisites, keeping it short of a 5.

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?

The core behavior is front-loaded and the sentences are tight in English. The fully duplicated Spanish translation doubles the length, which is redundant for an agent but not wasteful in content.

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?

With no output schema and no annotations, the description must explain return format, and it does (newline-separated lines, blanks removed, full-buffer default). Combined with 100% schema coverage and simple flat parameters, this is nearly complete, missing only device/permission context.

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 the baseline is 3. The description restates the cross-parameter rule (log_level requires filter_tag) and default behavior (full buffer), which the schema already documents, adding little net new meaning.

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?

States a specific verb (dumps) and resource (Android logcat buffer) and clarifies the mechanism (logcat -d; not a stream). This cleanly distinguishes it from sibling adb_clear_logcat and from streaming tools, so an agent can differentiate without opening a schema.

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?

Explains how to use the filters ('Use filter_tag alone for tag:*'; log_level only with filter_tag), which is usage context, but never states when to choose this over siblings like adb_execute_shell or adb_clear_logcat. Usage is implied rather than routed.

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