Skip to main content
Glama

adb_neighboring_cells

Lists all visible neighboring LTE/5G/WCDMA/GSM cells with identities and signal strengths to support cellular network surveys, coverage analysis, and radio environment characterization.

Instructions

List all visible cells beyond the serving cell: neighboring LTE/5G/WCDMA/GSM cells with their identities and signal strengths. Useful for cellular network surveys, coverage analysis, and radio environment characterization.

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

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.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; it does signal that this is a read-only enumeration and says what per-cell fields come back. It omits operationally important behavior: Android typically requires location permission for neighbor cell data, results may be sparse or empty depending on modem/network state, and no note is made about latency or modem prerequisites.

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 tight sentences with the resource and scope front-loaded and no redundant wording. The second sentence is use-case framing that is useful but slightly generic filler relative to 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 simple single-parameter read tool with no output schema, the description should sketch the return shape; it names identities and signal strengths but not the field set an agent would actually receive. The absence of any prerequisite or permission note leaves a gap an agent cannot fill from annotations or schema.

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 single optional `device` parameter is fully described in the schema (100% coverage), so the description adds nothing new about parameters and arguably does not need to. Baseline 3 applies because the schema already handles this.

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 uses a specific verb and resource ("List all visible cells beyond the serving cell") and enumerates the radio technologies and payload (identities, signal strengths). The phrase "beyond the serving cell" implicitly separates it from the serving-cell siblings such as adb_cell_identity, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

Three use cases are given (surveys, coverage analysis, radio environment characterization), which implies when to reach for the tool. However, there is no guidance on when NOT to use it or which sibling to prefer for serving-cell versus neighbor data, leaving the choice to inference from names alone.

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