Skip to main content
Glama
desamtralized

ADB Screenshot MCP Server

adb_list_devices

List all Android devices currently connected via ADB to identify available targets for remote management operations.

Instructions

List all connected ADB devices

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for adb_list_devices tool: executes 'adb devices' command and returns the stdout as text content.
    case "adb_list_devices": {
      const { stdout } = await execAsync("adb devices");
      
      return {
        content: [
          {
            type: "text",
            text: stdout,
          },
        ],
      };
    }
  • src/index.ts:70-78 (registration)
    Tool registration in ListToolsRequestSchema, including name, description, and empty input schema.
    {
      name: "adb_list_devices",
      description: "List all connected ADB devices",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe behavioral traits such as output format (e.g., list of device IDs), error handling (e.g., if no devices are connected), or performance characteristics (e.g., real-time vs. cached data). This leaves significant gaps for a tool with zero annotation coverage.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core purpose ('List all connected ADB devices'), making it easy to parse quickly. Every word earns its place, and there's no unnecessary elaboration.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states the purpose but lacks details on output format or behavioral context, which could be important for an agent to use it correctly. However, for a basic list operation, it meets the minimum viable threshold without being fully comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce confusion about inputs.

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 clearly states the verb ('List') and resource ('all connected ADB devices'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'adb_device_info' which might also provide device information, so it doesn't reach the highest score.

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 provides no guidance on when to use this tool versus alternatives like 'adb_device_info' or 'adb_connect_wifi'. It lacks any context about prerequisites (e.g., needing devices to be connected) or exclusions, leaving the agent to infer usage from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/desamtralized/adb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server