DroidPilot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | List connected Android devices and their state (device/unauthorized/offline). |
| launch_appA | Launch an app by its Android package name (e.g. 'life.overture.beam'). |
| stop_appC | Force-stop an app by package name. |
| screenA | Return a compact text list of the on-screen elements (label, tap point, id). Cheaper than a screenshot; use this to choose what to tap. |
| screenshotA | Capture the current screen as a PNG so you can visually inspect it. |
| tapC | Tap at absolute screen coordinates. |
| tap_textA | Tap the first element whose text/description contains |
| type_textB | Type text into the currently focused field. |
| press_keyA | Press a key: back, home, enter, tab, delete, menu, app_switch, or a raw KEYCODE_*. |
| swipeA | Swipe up, down, left, or right from the center of the screen. |
| wait_for_textC | Wait until an element containing |
| assert_textA | Assert that an element containing |
| screen_sizeA | Return the device screen size as 'WIDTHxHEIGHT'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool has a distinct, non-overlapping purpose: text assertion, app launch, device listing, key press, element retrieval, screenshot, screen size, app stop, swipe, coordinate tap, text tap, text typing, and wait. No two tools could be confused for the same action.
Most tools follow a verb_noun pattern (assert_text, launch_app, tap_text, etc.). However, 'screen' and 'screenshot' are nouns used as commands, and 'swipe' is a bare verb, introducing minor inconsistency.
13 tools cover the essential operations for Android device automation without being excessive. Each tool addresses a specific need, and the scope aligns well with the server's purpose.
The tool set covers core interactions (launch, stop, tap, type, swipe, screen inspection, waiting, assertion). Missing features like orientation control, clipboard operations, or scroll, but these are not critical for basic automation.