Skip to main content
Glama
Sign In
waydroid-mcp

waydroid-mcp

by TechyAditya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

session

Destructive

Starts, stops, or restarts the Waydroid Android environment; start waits for boot, and stop closes all Android apps.

Instructions

Starts, stops or restarts the Waydroid session. start waits until Android has booted (about 20-30 s). Stopping closes every Android app.

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": {
      "action": "<action>"
    },
    "name": "session"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
timeout_sNoHow long `start` waits for Android to boot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With only destructiveHint=true supplied, the description carries real weight and adds useful context: start blocks for roughly 20-30 s, and stop terminates every Android app, which explains why the tool is flagged destructive. It stops short of describing restart semantics or what happens to the session state during boot failure.

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?

Three short sentences, front-loaded with the core verb-and-resource statement, followed by the two facts that materially change behavior (boot wait, app termination). No filler or repetition of the schema.

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 two-parameter lifecycle tool with no output schema, this covers the essential behavior of two of the three actions and the destructive side effect. The 'restart' action is left undefined (whether it re-waits for boot, whether apps are closed), which is the one meaningful hole.

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 50%: the action enum and the timeout_s description are already documented in the schema. The description's timing note ('about 20-30 s') is helpful context for choosing timeout_s, but it never explains the unit relationship or what happens when the timeout expires, so added meaning is modest against the schema baseline.

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?

The description opens with a specific verb set and resource: 'Starts, stops or restarts the Waydroid session.' An agent immediately knows the domain and that the tool is a lifecycle controller. It does not explicitly differentiate itself from the sibling 'status' tool, keeping it just short of a 5.

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 implied by describing what each action does ('start waits until Android has booted', 'Stopping closes every Android app'), which helps the agent choose between actions. However, there is no explicit guidance on when to call this versus alternatives such as 'status' or when a restart is preferable to a stop/start pair.

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