Skip to main content
Glama

adb-device

Manage Android device connections for development tasks, including listing devices, selecting targets, checking properties, and monitoring device health.

Instructions

Manage device connections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
deviceIdNo

Implementation Reference

  • The main handler for the 'adb-device' tool, which routes requests to specific operation implementations.
    export async function handleAdbDeviceTool(
      input: AdbDeviceInput,
      context: ServerContext
    ): Promise<Record<string, unknown>> {
      const handler = operations[input.operation];
      if (!handler) {
        throw new ReplicantError(
          ErrorCode.INVALID_OPERATION,
          `Unknown operation: ${input.operation}`,
          "Valid operations: list, select, wait, properties, health-check",
        );
      }
      return handler(input, context);
    }
  • Schema definition for the inputs accepted by the 'adb-device' tool.
    export const adbDeviceInputSchema = z.object({
      operation: z.enum(["list", "select", "wait", "properties", "health-check"]),
      deviceId: z.string().optional(),
    });
  • Tool definition exported for registration, containing name, description, and input schema.
    export const adbDeviceToolDefinition = {
      name: "adb-device",
      description: "Manage device connections.",
      inputSchema: {
        type: "object",
        properties: {
          operation: {
            type: "string",
            enum: ["list", "select", "wait", "properties", "health-check"],
          },
          deviceId: { type: "string" },
        },
        required: ["operation"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: false,
        idempotentHint: false,
        openWorldHint: false,
      },
    };
Behavior1/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 disclosure but reveals nothing about side effects, state mutations, or which operations are safe versus destructive. The term 'manage' misleadingly suggests mutating operations, though the enum includes read-only operations like 'list' and 'health-check'. No error behaviors, rate limits, or return value descriptions are provided.

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

Conciseness2/5

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

At three words, the description is brief but constitutes under-specification rather than efficient communication. It fails to front-load critical information about the tool's diverse operational modes. The extreme brevity leaves significant gaps in understanding while not being usefully concise.

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

Completeness1/5

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

Given five distinct operations in the enum, two parameters, and zero schema documentation, the description is entirely inadequate to support correct tool invocation. It omits necessary context about return values, error states, and the specific Android device management domain. The complexity of the tool demands detailed explanation that is completely absent.

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

Parameters1/5

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

Schema description coverage is 0%, requiring the description to explain the operation enum values (list, select, wait, properties, health-check) and deviceId format, but it provides no parameter semantics whatsoever. The distinction between operations and their specific use cases is left entirely undocumented. The agent cannot determine valid inputs or operation purposes from the description alone.

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

Purpose3/5

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

The description 'Manage device connections' uses a vague verb without specifying the Android Debug Bridge context or what 'connections' entails. It fails to differentiate from sibling tools like emulator-device or adb-shell. While it hints at the general domain, the scope remains unclear.

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 emulator-device or adb-shell. It does not indicate prerequisites such as requiring a connected device or ADB server status. No exclusions or conditional usage patterns are mentioned.

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/thecombatwombat/replicant-mcp'

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