Skip to main content
Glama

Install APK from URL on device

device_install_apk_url

Download an .apk from a public https URL (max 100 MB) into AkaPhone storage and install it on a running device, then wait (up to 25 s) until the install succeeds or fails; if still installing, poll with device_list/screenshot or call again later. Runtime permissions are granted. .aab bundles are not supported: build a universal APK first. (The remote server cannot read local files; the stdio server's device_install_apk takes a file path instead.)

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>",
      "url": "<url>"
    },
    "name": "device_install_apk_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps URL of the .apk (e.g. a CI artifact or GitHub release asset)
device_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so: it discloses the 100 MB download cap, the 25 s internal wait and its failure/success semantics, that runtime permissions are granted, and that the remote server cannot read local files. These are the non-obvious constraints an agent could not infer from the schema.

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?

Every clause is load-bearing (limit, wait, recovery path, format restriction, server distinction) and the core action is front-loaded. The single long sentence with a trailing parenthetical is dense, but nothing is redundant.

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 two-parameter mutation tool with no output schema, it covers the full lifecycle an agent needs: prerequisite (running device), input constraints, timeout behavior, what to do on timeout, and the format caveat. Nothing needed to invoke it correctly is missing.

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%, so the description has to compensate for device_id, which it only implicitly covers by requiring a 'running device'. For url it adds real meaning beyond the schema: public https only, .apk extension, 100 MB ceiling, and example sources like CI artifacts or GitHub release assets.

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 opens with a specific verb chain (download + install) plus the exact resource (.apk from a public https URL) and the target (a running device). It is clearly distinguished from the only plausible sibling, device_install_apk, by noting that one takes a file path while this one fetches a URL.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when the tool applies (public https URL, <=100 MB, .apk), what to do during the wait window (poll with device_list/screenshot or call again later), and explicit exclusions (.aab bundles need a universal APK first). It even routes agents whose artifact is a local file to the stdio server's device_install_apk.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources