Skip to main content
Glama

Inspect Adb Device

inspect_adb_device
Idempotent

Reads a fixed getprop whitelist from one ADB device to report Android and SDK versions, security patch, fingerprint, CPU ABIs, and debuggable or emulator indicators without modifying the device.

Instructions

Inspect one device's build identity through a fixed getprop whitelist: Android and SDK versions, security patch, fingerprint, product identity, CPU ABIs, and debuggable flag, plus the observed emulator indicator ro.kernel.qemu. Read-only with respect to the device.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serial": "emulator-5554"
    },
    "name": "inspect_adb_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesDevice serial exactly as `adb devices` reports it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare openWorldHint=true, idempotentHint=true, destructiveHint=false, and readOnlyHint=false. The description adds useful behavioral context beyond annotations: it is limited to a fixed getprop whitelist, reports an observed emulator indicator, and is read-only with respect to the device. The phrase 'read-only with respect to the device' is not a direct contradiction of readOnlyHint=false because it qualifies scope; it clarifies that the tool may have non-device side effects while not mutating the device. It does not cover failure modes or authorization requirements, so a 4 rather than 5.

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?

The definition is a single, front-loaded sentence that states the operation, method, and returned fields without filler. It is dense but readable. Minor density could make it slightly harder to scan, but every element earns its place.

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?

No output schema exists, so the description must communicate return values, and it does by listing the whitelisted build properties and the emulator indicator. For a one-parameter inspection tool, the description covers purpose, data surface, and device read-only behavior well. It does not address error cases or adb authorization state, which prevents a 5.

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 one parameter, serial, and schema description coverage is 100%. The schema already explains that serial must match exactly what `adb devices` reports. The description says 'one device's' but adds no further meaning about the serial format or constraints beyond the schema, so baseline 3 is appropriate.

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 states a specific verb and resource: inspect one device's build identity via a fixed getprop whitelist. It enumerates the relevant properties (Android/SDK versions, security patch, fingerprint, product identity, CPU ABIs, debuggable flag, ro.kernel.qemu), making the purpose clear. It does not explicitly distinguish itself from sibling inspection tools such as inspect_adb_display or inspect_adb_package, so it falls short of a 5.

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 description implies when to use the tool by saying it retrieves build identity through getprop, which is useful context. However, it does not state explicit when-to-use versus when-not-to-use guidance, nor does it name alternative tools for related device inspection tasks. The usage is inferable but not proactively guided.

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