run-sequence-android-mcp

by nasiosheva

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Read Logcat

android_logcat

Read-only

Reads recent Android device logs and filters them by text or buffer to debug apps and capture crash reports.

Instructions

Read recent device logs. Useful for debugging apps (Flutter, React Native, native). The 'crash' buffer contains crash reports.

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": "android_logcat"
  }
}

Input Schema

Name	Required	Description
`lines`	No	Number of recent lines to fetch. Defaults to 200.
`buffer`	No	Log buffer to read. Defaults to 'main'. Use 'crash' for crash reports.
`device`	No	Device id (serial or host:port). Optional -- when omitted, uses ANDROID_MCP_DEVICE env or auto-selects the connected device (physical devices preferred over emulators).
`filter`	No	Only return lines containing this text (case-insensitive), e.g. a package name or 'flutter'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds valuable context about the crash buffer and debugging purpose, complementing the annotations without contradicting them.

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?

Two short, focused sentences. First sentence states purpose, second adds key detail on crash buffer. No unnecessary words.

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?

The description covers the core purpose and important parameter usage (crash buffer). It lacks details on output format, but with no output schema and simple log-line output, this is acceptable. Slightly less than ideal for a debugging tool.

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%, with each parameter well-documented. The description does not add significant additional meaning beyond the schema, only emphasizing the crash buffer. Baseline score of 3 is appropriate.

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?

Title 'Read Logcat' and description explicitly state the action (read) and resource (device logs). Mentions specific use cases (debugging Flutter, React Native, native) and distinguishes from sibling tools, none of which read logs.

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?

Description provides clear context: useful for debugging apps and mentions the crash buffer for crash reports. However, it does not explicitly state when not to use it or list alternatives among siblings, though no direct alternatives exist.

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