Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
phone_statusA

Is a phone connected? Shows model, Android version, how it is connected and what it can do. Call first; if nothing is connected it explains how to pair.

phone_screenA

Screenshot of the phone with every tappable element boxed and numbered, plus the element list as text. mode "grid" overlays lettered cells (A1 top-left) for spots without an element (games, maps, images); "both" draws both. Use phone_elements instead when text is enough.

phone_elementsA

Text list of what is on screen: numbered tappable elements, inputs, text and their positions. Cheaper than a screenshot. all=true also lists elements hidden under sheets or dialogs (for debugging).

phone_ocrA

Read the text drawn on the screen (on-device OCR) with positions. Use when something you can see in a screenshot is missing from phone_elements: many apps hide tab bars, rows or custom-drawn buttons from accessibility. phone_tap with that text also falls back to OCR automatically.

phone_tapB

Tap (or long-press) something on the phone. what to act on: element number from the last screen ("12"), grid cell ("C7"), pixel coordinates ("540,1200") or visible text ("Sign in"; text missing from the element list is found by OCR).

phone_typeA

Type text into an input (no keyboard tapping needed). Without target it types into the focused input. submit presses Enter/Search/Send afterwards.

phone_scrollA

Scroll the screen or one scrollable element. direction is where the content moves into view: "down" shows what is below.

phone_swipeB

Drag from one point to another (sliders, swipe-to-dismiss, custom gestures). from/to take the same targets as phone_tap.

phone_keyC

System buttons and keys: back, home, recents, notifications, quick_settings, enter, lock, power_dialog.

phone_open_appA

Open (launch) an installed app by its name ("WhatsApp") or package ("com.whatsapp"). With store=true, an app that is not installed is shown in the Play Store instead (nothing is installed automatically).

phone_volumeA

Read or change volume. stream: media (default), ring, notification, alarm, call, system. action: get, up, down, mute, unmute, max, a level number, or a percentage like "40%". Returns every stream level and the ringer mode.

phone_brightnessA

Read or set screen brightness: "get", 0–100, "auto" or "manual". Needs "Modify system settings" once (phone_permissions grant=true over USB, or the phone opens that settings page).

phone_toggleB

Quick device switches. flashlight: on|off. rotation: get|auto|portrait|landscape (needs "Modify system settings" once). dnd (Do Not Disturb): get|on|alarms|total|off (needs DND access once). ringer: get|normal|vibrate|silent.

phone_settingsA

Open a system settings page directly: settings, wifi, bluetooth, mobile-data, airplane, hotspot, nfc, location, display, sound, battery, storage, apps, notifications, security, privacy, accessibility, date, language, keyboard, developer, about, dnd, cast, vpn; Android 10+ panels: wifi-panel, internet-panel, volume-panel. Or app= for an app's info page (permissions, storage, force stop).

phone_open_linkA

Open a web page or a deep link on the phone (https://…, myapp://…, geo:lat,lng?q=…, mailto:…). package= forces a specific app (e.g. com.android.chrome).

phone_dialA

Open the phone dialer with a number filled in. It never places the call; the user presses call. If several dialer apps are installed, Android shows "Complete action using": tap one.

phone_web_searchB

Run a web search on the phone (opens the default search app or browser).

phone_device_infoC

Battery (level, charging, temperature, power saver, screen on), the app in front, and which permissions Agent Bridge has (system settings, Do Not Disturb, screen capture, gestures).

phone_notificationsC

Notifications that arrived on the phone since the Agent Bridge service started (app, text, time), newest first.

phone_clipboardA

Read the phone clipboard, or set it (set="text"). Android 10+ may hide the clipboard from background apps, so reading can come back empty.

phone_wakeA

Turn the screen on. A PIN, pattern or password lock stays locked: ask the user to unlock.

phone_permissionsB

Check what Agent Bridge is allowed to do. grant=true switches on the one-time permissions (Modify system settings, Do Not Disturb access) over USB with adb.

phone_send_filesA

Send files from this computer to the phone (absolute paths). They are saved in Downloads/Agent Bridge on the phone. Works over Wi-Fi or USB.

phone_received_filesB

Files the user sent from the phone to this computer (newest first) and the folder they are in, so you can open or read them.

phone_stop_appA

Force-stop an app by package (needs the phone on USB). Unsaved work in that app is lost.

phone_appsA

List installed apps that can be opened (name and package).

phone_wait_forB

Wait until some text appears on screen (page loads, messages arriving). Returns the element list.

Prompts

Interactive templates invoked by user choice

NameDescription
phone_tourConfirm the phone is connected and describe what is on screen right now.
do_in_appOpen an app on the phone and carry out a task in it, step by step.
test_my_appWalk through an app like a QA tester and report anything broken or confusing.
catch_upSummarise the notifications that arrived on the phone.
set_up_phoneChange volume, brightness, Do Not Disturb and other quick settings in one go.
send_to_phoneSend files from this computer to the phone and confirm where they landed.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 27 tools

Disambiguation4/5

Most tools target a distinct resource+action, and descriptions proactively explain boundaries (phone_screen vs phone_elements vs phone_ocr, phone_tap vs phone_swipe). The weaker spots are the informational trio phone_status / phone_device_info / phone_permissions, which overlap on connection and permission state, and phone_scroll vs phone_swipe, which both move content.

Naming Consistency4/5

All 27 tools share the phone_ prefix, giving a strong predictable family. Action naming is mostly verb_noun (phone_open_app, phone_stop_app, phone_send_files, phone_open_link), with a minority of bare-noun tools (phone_screen, phone_elements, phone_apps, phone_status) that read fine but break the pattern slightly.

Tool Count3/5

27 tools is at the heavy end for a single-purpose bridge, and a few (phone_ocr, phone_wait_for, phone_web_search, phone_dial) feel like conveniences layered on top of a core tap/type/screen loop. Most tools do earn their place given the breadth of device control, so it is borderline rather than bloated.

Completeness4/5

The surface covers the full device-automation lifecycle: discovery, UI reading, input, navigation, apps, files both directions, settings, toggles, notifications, clipboard and permissions. Gaps are minor and partly intentional (no direct call placement, no app install/uninstall, no SMS or contacts), which agents can route around via deep links or the UI.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues