Capture Android logcat output with filters for PID, tags, severity, and package, bounded by size, lines, or duration, and optionally redacted to focus on relevant logs.
Capture bounded, filtered, and redacted logcat output.
| Name | Required | Description | Default |
|---|---|---|---|
| pid | No | ||
| tags | No | ||
| since | No | ||
| severity | No | ||
| max_bytes | No | ||
| max_lines | No | ||
| duration_ms | No | ||
| package_name | No | ||
| include_crash_buffer | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that output is bounded, filtered, and redacted, which goes beyond the readOnlyHint annotation by specifying behavioral characteristics of the captured output. It does not contradict the annotation and adds context about the tool's constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, compact sentence that immediately states the tool's purpose. Every word contributes meaning, with no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of 9 optional parameters with no schema descriptions and no output schema, this one-sentence description is too minimal. It does not explain return format, device prerequisites, or how parameters map to the filtering/bounding behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0% description coverage for its 9 parameters, and the description does not mention any parameter names or explain their semantics. The phrase 'bounded, filtered, and redacted' only generically hints at filtering and size limits, leaving the agent to infer meaning from parameter names alone. This is insufficient for a tool with this many parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Capture' and identifies the resource as 'logcat output' with modifiers 'bounded, filtered, and redacted' that clarify the tool's scope. This distinguishes it from the sibling 'logcat_crashes', which appears focused on crash logs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance is provided regarding when to use this tool vs alternatives such as 'logcat_crashes'. The description lacks any mention of prerequisites, device selection, or comparison with other logging tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/EF-Code/scrcpy-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server