Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DROIDPATH_DISABLE_SEED_GRAPHNoOptional. Set to 1 to disable loading the built-in zero-PII Android Settings seed graph on cold start.

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

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
android_navigate_to_nodeB

Layer 3 Persistent A* Symbolic UI Router. Computes the shortest path across known screens in the Spatial Graph and executes taps/swipes via live Shadow DOM feedback without intermediate LLM calls.

android_explore_and_clickA

Dynamic Shadow DOM discovery + click with optional A* graph/prefix routing, bounded list scrolling (down/up), hazardous action HITL guard, and automatic Spatial Graph edge recording. Returns top-20 PII-redacted interactive candidates (needs_selection, isError: false) if no confident match is found.

android_get_ui_treeB

Reads interactive Android UI elements from the sub-millisecond Kotlin Shadow DOM stream (falls back to uiautomator XML if daemon stream is cold).

android_graph_statsB

Returns Spatial Graph telemetry: learned screen vertices, action edges, active canonical layout hash, daemon state, and persisted graph path.

android_list_devicesA

Lists connected Android devices visible over USB or Wireless ADB.

android_tap_elementA

Taps an Android UI element by coordinates (x, y) or semantic text / resource_id / content_desc, recording the transition edge into the Spatial Graph.

android_swipeC

Performs a touch swipe from (x1, y1) to (x2, y2) and attributes the action to the Spatial Graph.

android_type_textA

Types ASCII or Unicode text into the focused Android input field with optional press_enter.

android_keyeventB

Sends an Android keyevent (e.g. HOME, BACK, ENTER, APP_SWITCH, POWER).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 9 tools

Disambiguation4/5

The nine tools cover distinct layers: symbolic A* routing (navigate_to_node), dynamic discovery with optional routing (explore_and_click), raw element lookup (get_ui_tree), and a manual low-level tap (tap_element). There is some residual overlap since navigate_to_node, explore_and_click, and tap_element can all end in a tap, but the descriptions clearly delineate graph-routing vs. discovery vs. direct targeting.

Naming Consistency4/5

All tools share the android_ prefix and snake_case, with most following a verb_noun shape (android_tap_element, android_swipe, android_list_devices). Minor deviations exist in noun-only forms like android_graph_stats and android_keyevent, but the convention remains predictable.

Tool Count5/5

Nine tools is a well-scoped surface for an Android automation server, with each tool earning its place across graph routing, discovery, introspection, and primitive input actions. No redundant or filler tools are present.

Completeness3/5

Core interaction primitives (tap, swipe, type, keyevent, navigate, explore, UI tree, device listing) are covered, but notable gaps remain for an Android automation domain: no screenshot or visual capture, no app launch/package management, and no explicit wait-for-element or long-press/lifecycle operations.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues