mobilerun-mcp

Setup Portal

setup_portal

Install and enable the Mobilerun Portal on a device, optionally using a specific APK, to enable AI-driven control.

Instructions

Install and enable the Mobilerun Portal on the device (mobilerun setup); path installs a specific Portal APK.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "setup_portal"
  }
}

Input Schema

Name	Required	Description	Default
`path`	No
`device`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says the tool installs and enables software but omits side effects, whether the device must be connected/authorized, whether an existing Portal is replaced, and whether a restart or elevation is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence with the primary action front-loaded before the parameter caveat. No filler, though it could be marginally clearer with a short prerequisite clause.

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

Completeness2/5

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

An output schema exists, so return values need no explanation, but for a no-annotation mutation tool with an undocumented device parameter and no stated prerequisites, the definition is too thin to call the tool safely.

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 0%, so the description must explain both parameters. It clarifies that path installs a specific Portal APK, but the device parameter is left entirely undefined in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('install and enable') and resource ('Mobilerun Portal'), and explains the path parameter's effect. It does not differentiate itself from the nearby install_app sibling, which also installs software on the device.

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?

Conveys context implicitly through the '(mobilerun setup)' CLI hint and the two modes (default install vs path-specific APK), but never states when to prefer this over install_app or what prerequisites (connected device, permissions) must hold.

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

Deploy Server