Skip to main content
Glama

emulator-device

Manage Android emulators for testing and debugging applications through the replicant-mcp server. Create, start, control, and snapshot emulator instances to streamline development workflows.

Instructions

Manage Android emulators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYes
avdNameNo
deviceNoe.g., 'pixel_7'
systemImageNo
snapshotNameNo
emulatorIdNo

Implementation Reference

  • The main handler function for the 'emulator-device' tool, which dispatches based on the 'operation' field.
    export async function handleEmulatorDeviceTool(
      input: EmulatorDeviceInput,
      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, create, start, kill, wipe, snapshot-save, snapshot-load, snapshot-list, snapshot-delete",
        );
      }
      return handler(input, context);
    }
  • Input schema validation definition for the 'emulator-device' tool.
    export const emulatorDeviceInputSchema = z.object({
      operation: z.enum([
        "list",
        "create",
        "start",
        "kill",
        "wipe",
        "snapshot-save",
        "snapshot-load",
        "snapshot-list",
        "snapshot-delete",
      ]),
      avdName: z.string().optional(),
      device: z.string().optional(),
      systemImage: z.string().optional(),
      snapshotName: z.string().optional(),
      emulatorId: z.string().optional(),
    });
  • Tool definition registration for 'emulator-device'.
    export const emulatorDeviceToolDefinition = {
      name: "emulator-device",
      description: "Manage Android emulators.",
      inputSchema: {
        type: "object",
        properties: {
          operation: {
            type: "string",
            enum: [
              "list",
              "create",
              "start",
              "kill",
              "wipe",
              "snapshot-save",
              "snapshot-load",
              "snapshot-list",
              "snapshot-delete",
            ],
          },
          avdName: { type: "string" },
          device: { type: "string", description: "e.g., 'pixel_7'" },
          systemImage: { type: "string" },
          snapshotName: { type: "string" },
          emulatorId: { type: "string" },
        },
        required: ["operation"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
        idempotentHint: false,
        openWorldHint: false,
      },
    };
Behavior2/5

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

With no annotations provided, the description carries full burden but discloses nothing about behavioral traits. It fails to warn about destructive operations ('wipe' destroys data, 'kill' terminates instances) or explain snapshot persistence and side effects of 'create' vs 'start'.

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, it is technically brief but grossly under-specified rather than efficiently concise. For a tool with 9 distinct operations and 6 parameters, the single sentence fails to earn its place by providing actionable information.

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?

Completely inadequate for the complexity (6 parameters, 9 enum operations including destructive ones, no output schema). The description omits the operational model entirely (CRUD + snapshots + lifecycle) leaving the agent to guess at the tool's capabilities and requirements.

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 coverage is only 17% (only 'device' has a description). The description adds zero compensation for the undocumented parameters (avdName, systemImage, snapshotName, emulatorId) and does not explain critical relationships like which operation requires which parameters.

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

Purpose2/5

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

The description 'Manage Android emulators' is tautological and vague. While it identifies the domain (Android emulators), it fails to specify the management scope (lifecycle, snapshots, creation) and does not distinguish from sibling 'adb-device' which likely handles physical devices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

No guidance provided on when to use this tool versus 'adb-device' for physical devices, or prerequisites for operations (e.g., requiring SDK installation). No mention of operation-specific requirements or alternatives.

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