Skip to main content
Glama

adb_get_device_info

Retrieve detailed device information from Android devices connected via ADB, including specifications and status, for device management and automation tasks.

Instructions

Get detailed information about a specific device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdNoDevice ID (optional, uses default device if not specified)

Implementation Reference

  • The handler function that implements the core logic of the 'adb_get_device_info' tool by calling AdbClient.getDeviceInfo and formatting the response.
    async getDeviceInfo(deviceId?: string) {
      try {
        const deviceInfo = await this.adbClient.getDeviceInfo(deviceId);
        return {
          success: true,
          data: deviceInfo,
          message: `Device info retrieved for ${deviceInfo.id}`
        };
      } catch (error: any) {
        return {
          success: false,
          error: error.message,
          message: 'Failed to get device info'
        };
      }
    }
  • The input schema definition for the 'adb_get_device_info' tool, registered in the ListTools response.
    {
      name: 'adb_get_device_info',
      description: 'Get detailed information about a specific device',
      inputSchema: {
        type: 'object',
        properties: {
          deviceId: {
            type: 'string',
            description: 'Device ID (optional, uses default device if not specified)',
          },
        },
        required: [],
      },
    },
  • src/index.ts:435-436 (registration)
    The switch case that registers and dispatches calls to the 'adb_get_device_info' handler in the CallToolRequest handler.
    case 'adb_get_device_info':
      return await this.handleToolCall(this.deviceTools.getDeviceInfo(args?.deviceId as string));
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 the tool gets 'detailed information', but doesn't specify what that includes (e.g., model, status, properties), whether it's a read-only operation, or any error conditions. This leaves significant gaps in understanding the tool's behavior.

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 description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple tool, though it could be slightly more informative without losing conciseness.

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 detail what 'detailed information' entails, how results are structured, or potential errors. For a tool that retrieves device data, more context is needed to guide effective use.

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 input schema has 100% description coverage, with the 'deviceId' parameter documented as optional and defaulting to the default device. The description adds no additional meaning beyond this, as it doesn't explain parameter usage or constraints. Baseline 3 is appropriate since the schema handles 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 the resource 'detailed information about a specific device', making the purpose understandable. However, it doesn't distinguish this tool from similar siblings like 'adb_get_system_info' or 'adb_get_battery_info', which also retrieve device information but for different aspects.

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?

No guidance is provided on when to use this tool versus alternatives such as 'adb_get_system_info' or 'adb_get_battery_info', nor does it mention prerequisites like needing a connected device. The description implies usage for a 'specific device' but doesn't clarify if this is required or optional.

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/richard0913/adb-mcp'

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