replicant-mcp

adb-logcat

Read-onlyIdempotent

Read Android device logs and return a summary with logId. Filter by package, tags, severity level, or time range.

Instructions

Read device logs. Returns summary with logId.

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": {
      "lines": "<lines>"
    },
    "name": "adb-logcat"
  }
}

Input Schema

Name	Required	Description
`lines`	Yes	Default: 100
`package`	No
`tags`	No
`level`	No
`rawFilter`	No
`since`	No	e.g., '01-20 15:30:00.000'

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.6.7May 13, 2026
- addedInput schema / properties / lines / default
```
Added value: +100
```
- addedInput schema / required
```
Added value: +[
+  "lines"
+]
```
Changed5 schema fields changedv1.0.1Apr 2, 2026
- changedInput schema / properties / lines / description
```
Previous value: -"Number of lines (default: 100)"New value: +"Default: 100"
```
- removedInput schema / properties / package / description
```
Removed value: -"Filter by package name"
```
- removedInput schema / properties / rawFilter / description
```
Removed value: -"Raw logcat filter string"
```
- changedInput schema / properties / since / description
```
Previous value: -"Time filter (e.g., '5m' or ISO timestamp)"New value: +"e.g., '01-20 15:30:00.000'"
```
- removedInput schema / properties / tags / description
```
Removed value: -"Filter by log tags"
```
First observedv1.0.0Jan 21, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already indicate readOnly and idempotent, so the description adds minimal value. It does not explain what 'summary' means or any behavioral traits beyond reading logs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and efficient, but it sacrifices necessary detail. It is front-loaded but incomplete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 6 parameters and no output schema, the description is severely lacking. It does not explain how to filter logs, what the logId represents, or the return format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no meaning to the 6 parameters, especially the 4 undocumented ones (package, tags, level, rawFilter). Schema coverage is only 33%, and the description fails to compensate.

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?

The description clearly states the tool reads device logs, which is a specific verb+resource. However, it does not differentiate from siblings like adb-device or adb-shell, leaving ambiguity about the log source.

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?

No guidance is provided on when to use this tool versus alternatives. It lacks information about prerequisites, context, or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server