mobile-simulator-emulator-mcp

by gitsoufiane

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Boot Mobile Device

mobile_boot_device

Idempotent

Boot an iOS Simulator or Android virtual device and wait until it is fully ready for interaction.

Instructions

Boot an iOS Simulator or configured Android virtual device and wait until it is ready.

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": {
      "device": "<device>"
    },
    "name": "mobile_boot_device"
  }
}

Input Schema

Name	Required	Description	Default
`device`	Yes	Stable device ID returned by mobile_list_devices
`timeoutSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description states that the tool waits until the device is ready, which adds behavioral context beyond the annotations (idempotentHint: true, destructiveHint: false). It does not contradict annotations. However, it could elaborate on what 'ready' means (e.g., boot completion status).

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, 14-word sentence that is front-loaded with the key action and resource. No superfluous words or fluff.

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

Completeness3/5

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

The description is adequate for a simple boot operation but leaves open questions: What happens if boot fails? Does it throw an error? What does 'ready' mean? How long might it wait? The presence of annotations helps, but the description could be more thorough.

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

Parameters2/5

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

Schema coverage is 50% (only 'device' has a description). The description implicitly refers to the 'device' parameter ('Boot an iOS Simulator or configured Android virtual device'), but does not mention 'timeoutSeconds' or its semantics. With low coverage, the description should compensate for the undocumented parameter but does not.

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

Purpose5/5

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

The description clearly states that the tool boots an iOS Simulator or Android virtual device and waits until it is ready. The verb 'Boot' is specific and the resource 'device' is unambiguous. It distinguishes from siblings like mobile_launch_app (boots device vs. launches app).

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

Usage Guidelines3/5

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

The description implies the tool is used when you need to boot a device, but provides no explicit guidance on when to use it versus alternatives. It does not mention prerequisites (e.g., device must be configured) or when not to use it. Context is implied but not fully elaborated.

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

Deploy Server