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

mobile-simulator-emulator-mcp

by gitsoufiane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Terminate Mobile App

mobile_terminate_app
Idempotent

Terminate an iOS or Android app on a simulator or emulator by bundle ID or package name without clearing app data.

Instructions

Terminate an app by iOS bundle ID or Android package name without clearing app 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>",
      "appId": "<appId>"
    },
    "name": "mobile_terminate_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYes
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 declare destructiveHint=false and idempotentHint=true. The description adds that it does not clear app data, providing useful context beyond the annotations. No contradiction found.

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?

Single sentence with no extraneous information. Front-loaded with the action and key constraint. Every word serves a purpose.

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 two parameters and no output schema, the description covers the essential behavioral and parameter context. No missing information is evident.

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

Parameters4/5

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

Schema coverage is 50% (device described, appId not). The description adds meaning by specifying that appId can be an iOS bundle ID or Android package name, which helps the agent understand the parameter's usage beyond type constraints.

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 (terminate an app) and the method (by iOS bundle ID or Android package name). It also specifies a key behavioral detail (without clearing app data), which distinguishes it from siblings like mobile_reset_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 usage for termination without data clearance but does not explicitly state when to use or not use this tool versus alternatives. No exclusion or alternative references provided.

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