Skip to main content
Glama

adb_signal_detail

Retrieves detailed radio signal measurements—RSRP, RSRQ, SINR, RSSI, timing advance, and signal bars—from an Android device to support signal analysis and anomaly detection.

Instructions

Get detailed signal strength measurements: RSRP, RSRQ, SINR, RSSI, timing advance, and signal bars. Provides raw radio measurements for signal analysis and anomaly detection.

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

Input Schema

NameRequiredDescriptionDefault
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?

No annotations are provided, so the description carries the full behavioral burden and it under-delivers. It implies a read-only measurement fetch, but says nothing about prerequisites (root, modem availability), what happens on Wi-Fi-only devices or emulators with no radio, error/failure behavior, or whether measurements are instantaneous samples versus averaged. Only the set of returned metrics is disclosed.

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 concrete metric list, with no filler or repetition. The second sentence is somewhat generic ('Provides raw radio measurements...') but does add a use-case anchor rather than restating the first.

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 one-parameter read tool with no output schema, the description is adequate but leaves real gaps: it lists metric names without units, return structure, or sample semantics, and does not address the common failure case of devices without a cellular modem. An agent could call it correctly but may misinterpret the numbers it receives.

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?

There is a single parameter whose schema description ('Device serial') already achieves 100% coverage, so the schema does the work. The description adds no meaning about the device argument — not whether it can be omitted to target the sole connected device (0 required params) nor how multi-device targeting resolves.

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?

The description names a specific verb and resource ('Get detailed signal strength measurements') and enumerates the exact metrics returned (RSRP, RSRQ, SINR, RSSI, timing advance, signal bars), which distinguishes it reasonably well from broad siblings like adb_telephony. It stops short of explicitly differentiating itself from narrower radio siblings such as adb_cell_identity, adb_baseband_info, or adb_neighboring_cells.

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 through the phrase 'for signal analysis and anomaly detection' — that hints at context but gives no explicit when-to-use or when-not-to-use guidance. There is no mention of which sibling to prefer for cell identity, baseband, or full telephony dumps, even though many near-neighbors exist in the tool list.

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