Skip to main content
Glama

adb_modem_logs

Capture modem and baseband logs from RIL logcat, telephony framework, and kernel dmesg sources to diagnose radio issues and trace baseband-framework communication.

Instructions

Capture modem/baseband-related logs from multiple sources: RIL (Radio Interface Layer) logcat, telephony framework logs, and kernel modem messages via dmesg (root required for dmesg). Useful for radio diagnostics and tracing baseband-framework communication.

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_modem_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
grepNoAdditional grep filter applied to all sources
linesNoMax lines per log source (1-5000, default 200)
deviceNoDevice serial

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

B3.2/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 behavioral burden. It usefully flags that dmesg requires root, but never says whether this is a one-shot snapshot or a blocking capture, how long it runs, what happens if one source fails (partial results?), or whether root is needed for the other sources. For a multi-source capture tool this leaves significant unknowns.

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?

Two sentences, front-loaded with the action and source list, with the root caveat placed inline where it matters. Slightly dense (the RIL parenthetical and the diagnostics rationale could be trimmed) but no wasted framing.

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

Completeness3/5

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

There is no output schema and no annotations, so the description is the only place an agent can learn the shape of the result — yet it never says how the three sources are returned (merged? sectioned?), which matters for a multi-source tool. Adequate on what it captures, incomplete on what comes back.

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 coverage is 100% — grep, lines, and device are all documented with defaults and bounds — so the schema does the heavy lifting. The description adds nothing about parameter behavior, such as whether grep applies server-side across all three sources or whether device defaults to the sole connected device. Baseline 3 applies.

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?

Specific verb (capture) plus resource (modem/baseband logs) and an explicit enumeration of the three sources: RIL logcat, telephony framework logs, and kernel modem dmesg. It does not, however, distinguish itself from near siblings such as adb_ril_poll, adb_telephony, adb_logcat, or adb_baseband_info, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closing clause ('useful for radio diagnostics and tracing baseband-framework communication') implies the use case but never states when to choose this over adb_ril_poll/adb_ril_start or adb_logcat, nor any prerequisites beyond root for dmesg. Usage is implied rather than prescribed.

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