Skip to main content
Glama

adb_logcat_stop

Stops a running logcat watcher session by session ID, or stops all active sessions, to halt Android log capture.

Instructions

Stop a running logcat watcher session

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session": "<session>"
    },
    "name": "adb_logcat_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYesSession ID to stop (e.g., 'watch_1'), or 'all' to stop all

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 supplied, so the description carries the full burden of behavioral disclosure, and it states only 'stop'. It does not say whether the call is idempotent, what happens if the session ID is unknown or already stopped, whether buffered logs are discarded or retained for adb_logcat_poll, or what the response contains.

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?

One short, front-loaded sentence with no filler or redundant phrasing. It is efficient, though its brevity borders on under-specification rather than tight writing.

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 single-parameter session-stopper with fully documented schema and no output schema, the description is minimally adequate. It omits the post-stop consequences (session cleanup, error behavior, the 'all' bulk effect) that an agent would want before invoking it.

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% and the 'session' parameter already documents the 'watch_1' ID format and the 'all' wildcard. The description adds no meaning beyond that, so the baseline 3 applies.

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?

A specific verb ('Stop') plus a specific resource ('a running logcat watcher session') makes the operation unambiguous. It does not distinguish itself from nearby siblings such as adb_logcat_clear, adb_logcat_sessions, or adb_logcat_poll, so an agent must infer the boundary rather than read it.

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?

The sentence describes only what the tool does, giving no explicit when-to-use guidance. It never mentions that adb_logcat_sessions lists live sessions or that adb_logcat_clear handles buffer clearing, so an agent has no stated rule for choosing among the logcat family.

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