Skip to main content
Glama

List Adb Directory

list_adb_directory
Idempotent

Lists the immediate children of an absolute Android device directory via ADB, including hidden entries, metadata, and symlink targets, for read-only device file inspection.

Instructions

List the immediate children of one absolute device directory, including hidden entries: names, kinds, permissions, owner, group, sizes, dates, and symlink targets. Names and targets preserve embedded newlines. Recognizes the standard errors for absent paths and denied reads. 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",
      "device_path": "/data/data/com.example.app"
    },
    "name": "list_adb_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesDevice serial exactly as `adb devices` reports it
device_pathYesAbsolute device directory path to list, including hidden children

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior1/5

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

The description ends with 'Read-only,' while annotations declare readOnlyHint=false, a direct contradiction of the safety profile. The surrounding detail (error recognition for absent paths and denied reads, newline preservation) is genuinely useful, but the conflicting read-only claim is the kind of mismatch that misleads an agent about side effects.

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?

Three tight sentences, front-loaded with the core action and then the return shape, with no filler. The final 'Read-only' fragment is the one sentence that does not earn its place, since it conflicts with the annotations.

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?

There is no output schema, and the description does a good job enumerating returned fields (names, kinds, permissions, owner, group, sizes, dates, symlink targets) plus newline handling and error cases. However, the incorrect read-only claim leaves an agent uncertain about the tool's side-effect profile, which is a material gap for a two-parameter device tool.

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 description coverage is 100%, so both parameters are fully documented in the schema, which sets the baseline at 3. The description reinforces the path semantics ('one absolute device directory', hidden children included) but adds nothing about the serial parameter.

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?

States a specific verb and resource -- 'List the immediate children of one absolute device directory' -- which is scoped precisely enough to separate it from list_adb_devices (devices) and pull_adb_file (content). It stops short of explicitly naming a sibling to contrast with, which keeps it from 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to pick this tool over list_adb_devices, pull_adb_package, or any other listing sibling, and offers no prerequisites or exclusions. Usage is only inferable from the resource noun itself.

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