Skip to main content
Glama

adb_ril_start

Start capturing RIL messages from the radio logcat buffer to diagnose network registration, signal strength, authentication, handover, and NAS events.

Instructions

Start capturing RIL (Radio Interface Layer) messages from the radio logcat buffer. Captures network registration, cell info, signal strength, authentication, handover, and NAS events. Useful for radio diagnostics and cellular network research.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
bufferSizeNoMax messages to keep in ring buffer (100-50000, default 5000)
includeKernelNoAlso capture from main and kernel logcat buffers for modem framework and kernel-level radio messages

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?

With no annotations, the description carries the full burden, and it omits the important behavior: that this opens a stateful background capture session, whether the capture survives until adb_ril_stop, what happens if a capture is already running, whether root/privileged access is needed to read the radio buffer, and what the call returns. It only discloses the capture content.

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?

Three tightly written sentences, front-loaded with the action and resource. The final 'useful for...' sentence is the only one that borders on filler, but it adds legitimate domain context at low cost.

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

Completeness2/5

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

For a start-of-session tool that is part of a start/poll/stop triplet, with no annotations and no output schema, the definition leaves out session lifecycle, return value, and prerequisites. The capture-scope enumeration is good, but an agent cannot call this correctly without inferring that it must be followed by adb_ril_poll and adb_ril_stop.

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 all three parameters (device, bufferSize, includeKernel) are thoroughly documented in the schema, so the baseline is 3. The description adds nothing about parameter meaning — buffer size, ring-buffer overflow behavior, and the includeKernel tradeoff are left entirely to the schema.

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?

States a specific verb ('Start capturing') and a specific resource ('RIL messages from the radio logcat buffer'), plus enumerates the event types captured (registration, cell info, signal strength, NAS). This clearly separates it from generic adb_logcat_start, but it never names the paired siblings adb_ril_poll/adb_ril_stop, so an agent must infer the lifecycle.

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 only usage signal is the vague 'useful for radio diagnostics and cellular network research' — no explicit when-to-use, no when-not-to-use (e.g., versus adb_logcat_start or adb_modem_logs), and crucially no instruction that captured messages must be retrieved with adb_ril_poll and the session closed with adb_ril_stop.

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