Skip to main content
Glama
Sign In
waydroid-mcp

waydroid-mcp

by TechyAditya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

install_apk

Installs an APK or split app bundle from a host path or HTTP(S) URL, replaces the existing version by default, and returns the package name and version.

Instructions

Installs an APK, or a split bundle (.apks, .xapk, .apkm), from a host path or an http(s) URL. Replaces an installed version by default. Returns the package name and version.

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": {
      "source": "<source>"
    },
    "name": "install_apk"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesHost path or URL of the APK or bundle.
downgradeNo
allow_testNoAllow test-only APKs, as Android Studio debug builds are (-t).
extra_splitsNoMore split APK paths installed together with source.
grant_permissionsNoGrant all runtime permissions (-g).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does usefully flag the destructive default ('Replaces an installed version by default') and the return values, but it omits whether app data is preserved on replace, what failure looks like, and crucially that the 'downgrade' flag is the escape hatch for version downgrades.

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?

Three short sentences, front-loaded with the core action and scope, with zero filler. The replacement note and return-value note are both load-bearing.

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 five-parameter mutation tool with no annotations and no output schema, the definition is close to sufficient: it covers accepted formats, replacement behavior, and return values. It falls short only on the side effects of replacement (data retention) and the downgrade interaction.

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 coverage is 80%, so the baseline is 3. The description only restates the 'source' semantics (host path or URL) and says nothing about 'downgrade', 'allow_test', 'extra_splits', or 'grant_permissions' that the schema does not already explain better.

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 names a specific verb and resource ('Installs an APK, or a split bundle (.apks, .xapk, .apkm)') and states the accepted source types, so an agent knows exactly what the tool does and how it differs from launch_app, app_action, or app_info without opening the schema.

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?

Usage is only implied: 'from a host path or an http(s) URL' tells the agent what inputs are valid, but there is no explicit when-to-use framing, no prerequisites (connected device, source file must exist), and no mention of when to prefer launch_app or app_action over reinstalling.

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