MobAI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

install_app

Install a mobile app on an Android or iOS device using a local APK or IPA file path. Specify device ID and file path to complete installation.

Instructions

Install an app on the device from a local file path (.apk for Android, .ipa for iOS)

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_id": "<device_id>",
      "path": "<path>"
    },
    "name": "install_app"
  }
}

Input Schema

Name	Required	Description	Default
`device_id`	Yes	Device ID
`path`	Yes	Local file path to the app (.apk or .ipa)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.1Jun 10, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It mentions the input file types but fails to disclose important behavioral traits such as whether installation overwrites existing apps, requires permissions, or triggers a device restart. This lack of detail hampers agent decision-making.

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 concise sentence that immediately conveys the core action and method. No unnecessary words; the structure is front-loaded and efficient.

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 tool with only two required parameters and no output schema, the description covers the essential purpose and input details. It specifies platforms (.apk/.ipa), which adds useful context. However, it lacks discussion of result behavior (success/failure) or duration, but for a simple installation action, this is adequate.

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?

Schema description coverage is 100%, so the baseline is 3. The description redundantly notes file types already present in the schema and adds no new semantic information about the parameters.

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 ('install'), the resource ('app'), and the method ('from a local file path'), with specific file extensions for Android and iOS. It effectively distinguishes from sibling tools like 'uninstall_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 when installing an app from a local path, but lacks explicit guidance on when to use this tool versus alternatives, prerequisites, or when not to use it. The context of siblings like 'debug_app' suggests different purposes, but no direct exclusions are provided.

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