Skip to main content
Glama

adb_cell_identity

Extract cellular cell identity details such as CID, TAC/LAC, EARFCN/ARFCN, PCI, PLMN, and network type from Android dumpsys data for network analysis.

Instructions

Extract detailed cell identity information: Cell ID (CID), TAC/LAC, EARFCN/ARFCN, Physical Cell ID (PCI), PLMN, and network type. Parses structured data from dumpsys for cellular network analysis.

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

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.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the data source ('parses structured data from dumpsys') and implies a read-only extraction, but says nothing about failure modes (Wi-Fi-only device, no SIM, airplane mode), permissions, or whether the result is a single cell or a list — all material for a telephony probe.

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 compact sentences, front-loaded with the field list, with no filler. The phrase 'detailed cell identity information' is slightly redundant with the field enumeration that follows, but nothing else wastes space.

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

Completeness4/5

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

With no output schema, the field enumeration effectively serves as a return-value description, which is a genuine strength. The remaining gap is environmental preconditions and the list-vs-scalar shape of the result, which an agent would need before relying on it.

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 ('device') with 100% schema description coverage, so the schema already documents it. The description adds no meaning about the parameter, such as whether the device is optional or what happens when it is omitted; baseline 3 is appropriate when the schema does the work.

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 opens with a specific verb and resource ('Extract detailed cell identity information') and enumerates the exact data points returned (CID, TAC/LAC, EARFCN/ARFCN, PCI, PLMN, network type), so an agent knows precisely what this produces. It does not, however, distinguish itself from close telephony siblings such as adb_signal_detail, adb_neighboring_cells, or adb_telephony.

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 by the closing clause 'for cellular network analysis', which signals the general context. There is no explicit when-to-use statement, no prerequisites (e.g. active SIM, cellular-capable device), and no pointer to the sibling tools that handle signal strength or neighbor measurements instead.

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