Android UI Assist MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| take_android_screenshotC | Capture a screenshot from an Android device or emulator |
| list_android_devicesB | List all connected Android devices and emulators |
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 2 tools
The two tools have completely distinct purposes with no overlap: one lists devices, the other captures screenshots. An agent can easily differentiate between them based on their clear, specific functions.
Both tools follow a consistent verb_noun pattern (list_android_devices, take_android_screenshot) with the same prefix 'android_' for domain specificity. The naming is perfectly uniform and predictable.
With only two tools, the server feels under-scoped for an 'Android UI Assist' purpose, which typically implies broader UI interaction capabilities like clicking, typing, or inspecting elements. The count is too low for the apparent domain.
For an Android UI assistance server, there are significant gaps: no tools for interacting with UI elements (e.g., tap, input text), navigating apps, or retrieving UI hierarchies. The current tools only cover device listing and screenshot capture, leaving core UI automation workflows incomplete.