Skip to main content
Glama
desamtralized

ADB Screenshot MCP Server

adb_device_info

Retrieve information about connected Android devices, including device ID and status, to identify and manage devices for remote operations.

Instructions

Get information about a connected device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idNoDevice ID/serial (optional, uses first device if not specified)

Implementation Reference

  • Executes the adb_device_info tool by fetching device model, Android version, and API level using ADB getprop commands and returns formatted text output.
    case "adb_device_info": {
      const { device_id } = args as {
        device_id?: string;
      };
    
      const deviceArg = device_id ? `-s ${device_id}` : "";
      
      const [model, android, api] = await Promise.all([
        execAsync(`adb ${deviceArg} shell getprop ro.product.model`),
        execAsync(`adb ${deviceArg} shell getprop ro.build.version.release`),
        execAsync(`adb ${deviceArg} shell getprop ro.build.version.sdk`),
      ]);
    
      const info = {
        model: model.stdout.trim(),
        android_version: android.stdout.trim(),
        api_level: api.stdout.trim(),
      };
    
      return {
        content: [
          {
            type: "text",
            text: `Device Information:\nModel: ${info.model}\nAndroid Version: ${info.android_version}\nAPI Level: ${info.api_level}`,
          },
        ],
      };
    }
  • src/index.ts:98-111 (registration)
    Registers the adb_device_info tool in the ListToolsRequestSchema response, defining its name, description, and input schema.
    {
      name: "adb_device_info",
      description: "Get information about a connected device",
      inputSchema: {
        type: "object",
        properties: {
          device_id: {
            type: "string",
            description: "Device ID/serial (optional, uses first device if not specified)",
          },
        },
        required: [],
      },
    },
  • Input schema definition for the adb_device_info tool, specifying optional device_id parameter.
    inputSchema: {
      type: "object",
      properties: {
        device_id: {
          type: "string",
          description: "Device ID/serial (optional, uses first device if not specified)",
        },
      },
      required: [],
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it gets information but doesn't disclose behavioral traits such as what type of information is returned (e.g., device status, properties), whether it requires specific permissions, or if there are rate limits. This is a significant gap for a tool with no 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 appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what information is returned or any behavioral context, which is inadequate for a tool that interacts with devices. More detail is needed to compensate for the missing structured data.

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?

The schema description coverage is 100%, with the parameter 'device_id' fully documented in the schema. The description adds no additional meaning beyond the schema, such as examples or context for the optional parameter. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Get') and resource ('information about a connected device'), making the purpose immediately understandable. It doesn't specifically differentiate from siblings like 'adb_list_devices' (which might list multiple devices versus getting detailed info about one), but it's not vague or tautological.

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. It doesn't mention siblings like 'adb_list_devices' for listing devices or 'adb_screenshot' for other device operations, nor does it specify prerequisites (e.g., device must be connected).

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