Skip to main content
Glama
mobile-next

Mobile Next MCP Server

Official
by mobile-next
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Launch App

mobile_launch_app

Launch a mobile app on a specified device using its package name, with an optional locale parameter to control the app's language settings.

Instructions

Launch an app on mobile device. Use this to open a specific app. You can find the package name of the app by calling list_apps_on_device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceYesThe device identifier to use. Use mobile_list_available_devices to find which devices are available to you.
localeNoComma-separated BCP 47 locale tags to launch the app with (e.g., fr-FR,en-GB)
packageNameYesThe package name of the app to launch

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.0.53
    • addedInput schema / properties / locale
      Added value: +{
+  "description": "Comma-separated BCP 47 locale tags to launch the app with (e.g., fr-FR,en-GB)",
+  "type": "string"
+}
  2. Changed3 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / device
      Added value: +{
+  "description": "The device identifier to use. Use mobile_list_available_devices to find which devices are available to you.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "packageName"
-]New value: +[
+  "device",
+  "packageName"
+]
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is already covered. The description adds no behavioral details beyond the launch action itself, such as foregrounding behavior or failure conditions. It does not contradict annotations, but it does not go beyond them in disclosing side effects.

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 with no filler. The primary action is front-loaded, and the additional guidance about finding the package name is placed efficiently. Every word contributes to clarity.

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

Completeness4/5

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

For a simple launch tool with three parameters and no output schema, the description covers the purpose, the precondition for packageName, and the device parameter is covered by the schema. It does not mention error handling or edge cases, but that is not critical for this type of tool. It is sufficiently complete.

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 100%, so all parameters are described. The description adds a useful hint for the packageName parameter by referencing list_apps_on_device, which helps the agent obtain the correct value. This goes beyond the schema's basic description, adding practical guidance.

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 ('Launch an app on mobile device') with a specific verb and resource. It distinguishes this from sibling tools like install, terminate, or open URL by its explicit purpose. The mention of finding package names via list_apps further clarifies its scope.

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 says 'Use this to open a specific app', which gives a clear use case. It also provides a precondition (find package name) but does not explicitly exclude alternatives like mobile_open_url or mobile_terminate_app. It could be more explicit about when not to use, but the guidance is adequate.

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