replicant-mcp

emulator-device

Destructive

List, create, start, stop, wipe, and manage snapshots for Android emulators in the development environment.

Instructions

Manage Android emulators.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation": "<operation>"
    },
    "name": "emulator-device"
  }
}

Input Schema

Name	Required	Description
`operation`	Yes
`avdName`	No
`device`	No	e.g., 'pixel_7'
`systemImage`	No
`snapshotName`	No
`emulatorId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.1Apr 2, 2026
- removedInput schema / properties / avdName / description
```
Removed value: -"AVD name"
```
- changedInput schema / properties / device / description
```
Previous value: -"Device profile (e.g., 'pixel_7')"New value: +"e.g., 'pixel_7'"
```
- removedInput schema / properties / emulatorId / description
```
Removed value: -"Running emulator ID"
```
- removedInput schema / properties / snapshotName / description
```
Removed value: -"Snapshot name"
```
- removedInput schema / properties / systemImage / description
```
Removed value: -"System image"
```
First observedv1.0.0Jan 21, 2026

TDQS

C2/5.0

Behavior2/5

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

Annotations indicate destructiveHint: true and readOnlyHint: false, which is helpful, but the description adds no context about side effects, required permissions, or which operations are destructive. The description does not elaborate beyond what annotations already provide.

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?

The description is extremely concise but at the cost of under-specification. Every sentence should earn its place; here, the single sentence is too vague to be useful.

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?

With no output schema and sparse annotations, the description fails to cover essential context such as return values, error conditions, or prerequisites for the various operations. It is inadequate for a multi-operation tool.

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 only 17%, with only one parameter ('device') having a brief example. The description does not explain the meaning or format of any other parameters (avdName, systemImage, snapshotName, emulatorId), leaving the agent to guess.

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 states 'Manage Android emulators,' which identifies the resource but uses a vague verb. It is not specific to any single operation, and does not distinguish from sibling tools like adb-device.

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, nor any exclusions or prerequisites for specific operations. The agent receives no help in deciding context.

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

Deploy Server