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

mobile-simulator-emulator-mcp

by gitsoufiane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Reset Mobile App State

mobile_reset_app
Destructive

Reset an app to its initial state on Android or iOS. Clears app data on Android; uninstalls iOS apps for reinstallation.

Instructions

Clear Android app data or uninstall an iOS app. Reinstall the iOS app with mobile_install_app afterward.

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>",
      "appId": "<appId>"
    },
    "name": "mobile_reset_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYes
deviceYesStable device ID returned by mobile_list_devices

Output Schema

NameRequiredDescriptionDefault
appIdYes
resetYes
deviceYes
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true; description adds platform-specific details (clear data vs uninstall), providing useful behavioral context beyond annotations.

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?

Two concise sentences, front-loaded with the main action; no wasted words.

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 destructive reset tool with output schema present, description adequately covers platform behavior and follow-up, meeting completeness needs.

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 description coverage is 50% (only device described); description adds no parameter-specific details beyond schema, failing to compensate for the gap.

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?

Description clearly states platform-specific actions (clear Android data, uninstall iOS) and references reinstallation for iOS, distinguishing it from mobile_install_app.

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?

Explicitly states use case (reset app state) and mentions post-action for iOS (reinstall with mobile_install_app). Could be improved by excluding when not to use.

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