devilge

Overview Schema Source Related Servers Discussions Admin

Resize logcat ring buffer

devilge_resize_logcat_buffer

Idempotent

Increase the logcat ring buffer size to prevent recent logs from being evicted quickly when verbose Ktor logging is used. Applies to future captures only.

Instructions

Increase the device-side logcat ring buffer so that recent HTTP / app logs are not evicted within seconds. Applies to subsequent captures only — entries already lost are gone. Recommended whenever Ktor LogLevel.ALL produces dozens of lines per request.

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": {
      "sizeMb": "<sizeMb>"
    },
    "name": "devilge_resize_logcat_buffer"
  }
}

Input Schema

Name	Required	Description	Default
`serial`	No	Device serial. Defaults to DEVILGE_DEFAULT_DEVICE_SERIAL or the only attached device.
`sizeMb`	Yes	New logcat buffer size in MiB (1-256). 16 is a sensible default for verbose Ktor logging.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.3Jul 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description adds crucial behavioral context beyond annotations: the buffer resize applies only to future captures, and already lost entries are gone. This aligns with annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true) and provides transparency.

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?

The description is concise (two sentences) and front-loaded with the core purpose. It efficiently conveys key information, though a more structured format (e.g., bullet points) could improve readability.

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

Completeness5/5

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

Given the tool's simplicity (2 parameters, no output schema, clear annotations), the description covers all necessary aspects: purpose, usage context, behavioral effect, and parameter hints (default in schema). No gaps are present.

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?

The input schema covers 100% of parameters with clear descriptions, including a default for sizeMb. The tool description adds no extra meaning beyond what the schema provides, so baseline 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?

The title and description clearly state the action (increase/resize) and resource (logcat ring buffer), with a specific purpose: preventing log eviction. It distinguishes itself from sibling tools like devilge_get_logcat, which retrieves logs, by being a configuration tool.

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?

The description provides explicit guidance on when to use (Ktor LogLevel.ALL) and a caveat (effect only on subsequent captures). However, it does not mention alternatives or when not to use, which would make it a 5.

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