Skip to main content
Glama

adb_ril_poll

Retrieve captured Android RIL messages since the last poll, with optional category and message-count filters to inspect registration, signal, network, and radio-state data.

Instructions

Retrieve captured RIL messages since the last poll. Optionally filter by category (registration, cell_info, signal, network, security, handover, data, radio_state, nas).

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": {
      "session": "<session>"
    },
    "name": "adb_ril_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn raw logcat lines instead of parsed messages
sessionYesSession ID from adb_ril_start (e.g., 'ril_1')
categoryNoFilter by category: registration, cell_info, signal, network, security, handover, data, radio_state, sms, nas, other
maxMessagesNoMax messages to return per poll (1-10000)

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.4/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden, and it does disclose the most important behavioral trait: polling is incremental and consumes messages past the last poll. It does not say what happens to messages arriving between polls (buffer size, overflow/drop behavior), whether polling is destructive to the capture, or what the returned message shape looks like.

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 scope, with no filler. The parenthetical category list is the only mildly redundant part since the schema already enumerates them.

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?

For a stateful polling tool with no output schema, the definition should say that messages are drained between polls and hint at the lifecycle (start/stop). It covers the core retrieval semantics but leaves the session prerequisite and result/pagination behavior implicit, which are the details an agent most needs to call it repeatedly without losing data.

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%, so the schema already documents raw, session, category, and maxMessages; baseline is 3. The description restates the category list but omits 'sms' and 'other' that the schema enumerates, and says nothing about the raw flag or the maxMessages cap, so it adds no meaning beyond 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 and resource ('Retrieve captured RIL messages') plus the incremental scope ('since the last poll'), which is enough to distinguish it from adb_logcat_poll-style reading. It does not name its sibling lifecycle partners (adb_ril_start / adb_ril_stop) in the description, so full differentiation is left to the schema.

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?

Usage is only implied: 'since the last poll' signals a repeated, cursor-advancing read, but there is no explicit statement that a session must first be opened via adb_ril_start or that adb_ril_stop ends it. No guidance is given on when to use this versus adb_logcat_poll for the same underlying data.

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