AutoMobile
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 |
|---|---|
| observeC | Get the view hierarchy of what is displayed on screen |
| listAppsC | List all apps installed on the device |
| clearTextC | Clear text from the currently focused input field |
| selectAllTextA | Select all text in the currently focused input field using long press + tap on 'Select All' |
| pressButtonC | Press a hardware button on the device |
| swipeOnElementC | Swipe on a specific element |
| swipeOnScreenC | Swipe on screen in a specific direction |
| openSystemTrayA | Open the system notification tray by swiping down from the status bar |
| pressKeyB | Press a hardware key on the device (Maestro equivalent of pressButton) |
| inputTextC | Input text to the device |
| openLinkB | Open a URL in the default browser |
| tapOnD | Tap supporting text or resourceId |
| scrollC | Scroll in a direction on a scrollable container, optionally to find an element (supports text and selectors) |
| swipeC | Unified scroll command supporting direction and speed (no index support due to reliability) |
| shakeC | Shake the device |
| imeActionC | Perform an IME action (e.g., done, next, search) |
| recentAppsC | Open the recent apps list |
| homeScreenB | Return to the home screen by pressing the home button |
| rotateC | Rotate the device to a specific orientation |
| launchAppC | Launch an app by package name |
| terminateAppC | Terminate an app by package name |
| installAppC | Install an APK file on the device |
| enableDemoModeA | Enable demo mode with consistent status bar indicators for screenshots |
| disableDemoModeC | Disable demo mode and return to normal status bar behavior |
| setActiveDeviceC | Set the active device ID for subsequent operations |
| listDevicesC | List all connected devices (both physical and virtual devices) |
| listDeviceImagesB | List all available device images for the specified platform |
| startDeviceC | Start a device with the specified device image |
| killDeviceC | Kill a running device |
| setDeviceModeC | Set parameters for a particular device in a given mode. |
| setAppSourceC | For a given appId, set the source code path and platform. |
| getAllConfigsB | Retrieve current configuration. |
| resetConfigB | Reset to default settings. This will clear all saved configuration. |
| getDeepLinksC | Query available deep links and intent filters for an Android application |
| detectIntentChooserB | Detect system intent chooser dialog in the current view hierarchy |
| handleIntentChooserC | Automatically handle system intent chooser dialog with specified preferences |
| installPlatformDependenciesC | Install required dependencies and tools for the specified platform |
| checkPlatformDependenciesB | Check the installation status of platform dependencies and tools |
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 38 tools
Most tools have distinct purposes, but there is notable overlap between pressButton and pressKey (both press hardware buttons, with pressKey described as the 'Maestro equivalent'), and between scroll and swipe (both handle directional movement, with swipe described as a 'unified scroll command'). These overlaps could cause confusion for an agent trying to select the right tool.
Tool names are mostly consistent with a verb_noun pattern (e.g., clearText, installApp, launchApp), but there are minor deviations like observe (verb only) and getAllConfigs (verb_adjective_noun). Overall, the naming is readable and follows a predictable convention with only a few outliers.
With 38 tools, the count is excessive for an Android automation server, making it feel heavy and potentially overwhelming. A more focused set of 10-20 tools would be more appropriate for this domain, as many tools could be consolidated or omitted without losing functionality.
The tool surface is highly complete for Android device automation, covering installation, configuration, navigation, input, interaction, and device management. It includes CRUD-like operations (e.g., installApp, listApps, terminateApp) and supports core workflows without obvious gaps, ensuring agents can handle most automation tasks effectively.