Skip to main content
Glama
Sign In
mobile-debug-mcp

mobile-debug-mcp

by clivejefferies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

install_app

Install an Android or iOS app from a built binary or project directory, building first when needed. Specify platform and project type to select the correct build and install flow.

Instructions

Install an app on Android or iOS. Accepts a built binary (apk/.ipa/.app) or a project directory to build then install. platform and projectType are required.

Input Schema

NameRequiredDescriptionDefault
appPathYesPath to APK, .app, .ipa, or project directory
deviceIdNoDevice UDID (iOS) or Serial (Android). Defaults to booted/connected.
platformYesPlatform to install to (required).
projectTypeYesProject type to guide build/install tool selection (required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.34.0
    • addedInput schema / allOf
      Added value: +[
+  {
+    "not": {
+      "required": [
+        "expectedState"
+      ]
+    }
+  }
+]
  2. First observedv0.31.0

TDQS

A4.4/5.0
Behavior4/5

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

Since no annotations were provided, the description is vital. It successfully discloses a key behavioral trait: the tool can operate in a dual mode (install artifact OR build and then install project), which is a complex piece of operational knowledge.

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 definition is extremely concise, using two sentences to convey the core functionality, the two operational modes, and the requirements, with zero wasted words.

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?

Given the complexity of handling both binaries and source code, the description is very complete. The mention of specific file extensions and the distinction between build and install logic provides everything an agent needs to choose this tool correctly.

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?

While the schema defines `appPath` as a string, the description adds crucial meaning by clarifying that this path can represent either a final artifact (.apk, .ipa, etc.) or an entire project directory that needs to be compiled first.

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 defines the action (install app) and the scope (Android or iOS). Crucially, it distinguishes itself from siblings like `start_app` and `build_app` by specifying that it handles the full lifecycle, including building from a project directory.

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?

It provides explicit instructions on when to use the tool: when the user has either a ready-to-use binary OR a project that needs to be built and then installed. It also correctly notes that platform and projectType are mandatory.

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