Skip to main content
Glama
Neem2004

Android ADB MCP Server

by Neem2004
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

adb_get_logcat

Retrieve filtered Android logcat entries by tag, minimum log level, and line count to troubleshoot crashes and system events.

Instructions

Dumps the Android device logcat buffer, optionally filtered by tag, minimum log level and limited to the last N lines. / Vuelca el buffer de logcat del dispositivo Android, opcionalmente filtrado por tag, nivel mínimo de log y limitado a las últimas N líneas.

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. / Nivel mínimo de log a incluir (V=verbose … F=fatal). Requiere filter_tag para tener efecto.
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. 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"
+]
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It clearly indicates this is a dump/read operation, but it does not mention potential output size, default behavior when lines is omitted, or any prerequisites. The schema's lines default (200) conflicts with the phrase 'defaults to the full buffer,' adding ambiguity.

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?

The description is a single, front-loaded sentence with no filler. The bilingual translation is compact and mirrors the original without adding unnecessary detail or repetition beyond what localization requires.

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 simple read-only tool with three optional parameters and no output schema, the description covers the core action and filters. It is slightly incomplete because it does not specify default line behavior, and the ambiguous lines default could confuse an agent, but overall it provides sufficient context to invoke the tool correctly.

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 parameter concepts (tag, minimum log level, last N lines) but adds no new meaning beyond the property names and schema descriptions. It does not mention the dependency that log_level requires filter_tag, although the schema does.

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?

The description states a specific action ('Dumps') and resource ('Android device logcat buffer'), with clear filtering options. It implicitly distinguishes itself from sibling adb_clear_logcat by describing a read operation rather than a clear operation.

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 description implies when to use the tool—when you need to read the logcat buffer—but it does not explicitly state when not to use it or mention alternatives such as adb_clear_logcat. No exclusions or comparative guidance is provided.

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