Skip to main content
Glama
Sign In
mobile-simulator-emulator-mcp

mobile-simulator-emulator-mcp

by gitsoufiane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Shut Down Mobile Device

mobile_shutdown_device
Idempotent

Shut down a running iOS Simulator or Android Emulator without deleting its data. Requires the device ID from mobile_list_devices.

Instructions

Shut down a running iOS Simulator or Android Emulator without deleting its data.

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_shutdown_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceYesStable device ID returned by mobile_list_devices

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations indicate idempotent and non-destructive behavior. The description adds that it shuts down without deleting data, which is consistent and provides additional context. No contradictions or missing behavioral details for this simple tool.

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 sentence that efficiently conveys the purpose and key constraint. Every word earns its place with no redundancy or unnecessary detail.

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

Completeness5/5

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

For a simple tool with one parameter and no output schema, the description provides complete information about what the tool does and its non-destructive nature. The annotations further support this, making the definition adequate for selecting and invoking the tool.

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 for the single required parameter 'device', which is already described as 'Stable device ID returned by mobile_list_devices'. The description does not add new meaning beyond that, so baseline score of 3 is appropriate.

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 the action 'Shut down' and the specific targets 'iOS Simulator or Android Emulator'. It also includes the crucial constraint 'without deleting its data'. This distinguishes it from siblings like mobile_boot_device and mobile_erase_device.

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

Usage Guidelines4/5

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

The description implies usage when needing to stop a simulator/emulator while preserving data. It does not explicitly state when not to use or provide alternatives, but the context from sibling names like mobile_boot_device provides clear differentiation.

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

Deploy Server

Other Tools