Skip to main content
Glama

adb_logcat_start

Start a background Android logcat watcher that stores log lines in a ring buffer for later retrieval via polling.

Instructions

Start a background logcat watcher. Lines accumulate in a ring buffer. Use adb_logcat_poll to retrieve new 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_logcat_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoFilter by tag (e.g., 'MyApp'). Must match /^[a-zA-Z0-9_]+$/ — Android tags are identifier-shaped in practice.
deviceNoDevice serial
priorityNoMinimum priority level
bufferSizeNoMax lines to keep in ring buffer (100-50000, default 2000)

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. Changed3 schema fields changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / tag / description
      Previous value: -"Filter by tag (e.g., 'MyApp')"New value: +"Filter by tag (e.g., 'MyApp'). Must match /^[a-zA-Z0-9_]+$/ — Android tags are identifier-shaped in practice."
    • addedInput schema / properties / tag / pattern
      Added value: +"^[a-zA-Z0-9_]+$"
  3. First observedv1.1.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden and does disclose the key non-obvious traits: the watcher runs in the background, output accumulates rather than returning inline, and a ring buffer is involved. It stops short of the operational facts an agent most needs — that old lines are silently dropped when the buffer fills, that adb_logcat_stop is required to release the watcher, and what happens if start is called again while one is already running.

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 with the action front-loaded, the buffering behaviour second, and the follow-up tool last. Nothing is redundant and no sentence could be dropped without losing information.

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?

There is no output schema and all four parameters (none required) are fully described in the schema, so the description only needs to cover lifecycle and it does most of it: start, accumulate, poll. The missing piece is the stop/teardown half of the lifecycle, which matters for a long-running background watcher that consumes device-side resources.

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%: tag, device, priority enum, and bufferSize (with default 2000 and 100–50000 bounds) are all documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies — the schema, not the prose, does the parameter work.

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 opens with a specific verb+resource ('Start a background logcat watcher') and immediately distinguishes this tool from the one-shot sibling adb_logcat by naming adb_logcat_poll as its retrieval counterpart. An agent can tell what this does and which tool continues the workflow without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent to adb_logcat_poll for retrieval, which establishes the start-then-poll pattern. However, it never mentions adb_logcat_stop (the obvious cleanup partner) or says when to prefer this watcher over the plain adb_logcat dump, so the when-to-use vs. alternatives picture is only half-drawn.

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