Skip to main content
Glama

List Adb Features

list_adb_features
Idempotent

Lists a connected Android device’s declared hardware and software features via pm list features for read-only device fingerprinting.

Instructions

List the device's declared hardware and software features (pm list features) for device fingerprinting. Read-only.

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": "list_adb_features"
  }
}

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

B3.3/5.0
Behavior1/5

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

The description asserts 'Read-only', but the annotations declare readOnlyHint=false, a direct conflict about the tool's side-effect profile. Beyond that, it says nothing about behavior on an offline/unauthorized device or what the returned feature list looks like, so the description actively muddies rather than clarifies the declared behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the resource and command, then the purpose and safety claim. No filler or repetition.

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 full schema coverage and no output schema, the description is close to sufficient, but it omits failure modes (device offline, unauthorized) and the feature-string output format. The read-only claim also contradicts the annotations, leaving the agent with an unresolved safety picture.

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 coverage is 100% and the single `serial` parameter is already fully documented as the exact string from `adb devices`, with an example. The description adds no extra meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (device's declared hardware and software features), names the underlying command `pm list features`, and adds the analytical purpose (device fingerprinting). This clearly separates it from siblings like list_adb_packages or list_adb_devices.

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 phrase 'for device fingerprinting' implies the use case, so usage is inferable but never stated as when-to-use vs. when-not. No alternative tool is named for other feature-inspection or device-profiling needs, and no prerequisite (e.g., device must be connected/authorized) is given.

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