Skip to main content
Glama
DarkNoah
by DarkNoah

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AUTOGLM_MODELNoModel to useautoglm-phone
AUTOGLM_API_KEYYesYour AutoGLM API key
AUTOGLM_API_URLNoBase URL for AutoGLM APIhttps://open.bigmodel.cn/api/paas/v4

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
adb_connectA

Connect to an Android device via ADB over network.

This tool connects to an Android device using its IP address and port number. The device must have ADB over TCP/IP enabled.

Args:

  • address (string): Device address in format IP:PORT (e.g., 192.168.10.20:5555)

Examples:

  • address: "192.168.10.20:5555"

  • address: "10.0.0.100:5555"

Prerequisites:

  • The target device must have ADB debugging enabled

  • The device must have TCP/IP mode enabled (adb tcpip 5555)

  • The device must be reachable on the network

autoglm_list_adb_devicesA

List all Android devices connected via ADB (Android Debug Bridge).

This tool queries ADB to get a list of all connected Android devices, including their device IDs, status, connection type, model, and screen dimensions.

Device Status:

  • device: Device is connected and ready

  • offline: Device is connected but not responding

  • unauthorized: Device is connected but requires authorization

Connection Types:

  • usb: Connected via USB cable

  • wifi: Connected via WiFi

  • remote: Connected via remote ADB

Examples:

  • Use when: You need to check which Android devices are connected

  • Use when: You need to get device IDs for executing actions on specific devices

  • Use when: You need to verify ADB connection before executing actions

Error Handling:

  • Returns empty devices array if ADB is not installed or not accessible

  • Returns empty devices array if no devices are connected

autoglm_taskA

Execute a task on a connected device using AutoGLM online model.

This tool sends a natural language task description to the AutoGLM online model, which analyzes the current screen state and automatically performs the required actions to complete the task. The model will iteratively capture screenshots, analyze the screen, and execute actions until the task is complete or the maximum steps are reached.

Args:

  • device_id (string, optional): Target ADB device ID (if not specified, uses the first connected device)

  • prompt (string): Natural language task description for AutoGLM to execute (1-5000 characters)

  • max_steps (number, optional): Maximum number of steps to execute (default: 100, range: 1-200)

  • lang ('cn' | 'en', optional): Language for system prompt and responses (default: 'cn')

How it works:

  1. Captures the current screen via ADB

  2. Sends the screen image and task prompt to AutoGLM online model

  3. The model analyzes the screen and decides on the next action

  4. Executes the action via ADB

  5. Repeats until the task is complete or max_steps is reached

Examples:

  • Use when: "Open WeChat and send a message to Mom saying hello"

  • Use when: "Order a coffee from Starbucks app"

  • Use when: "Navigate to the settings and enable dark mode"

  • Don't use when: You only need to execute a single known action (use autoglm_execute_action instead)

Error Handling:

  • Returns "Error: No ADB devices connected" if no device is available

  • Returns "Error: API authentication failed" if API key is invalid

  • Returns "Error: Task execution failed" if the task cannot be completed

  • Returns partial results if the task is interrupted

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation4/5

The three listed tools are clearly separated: connecting to a device, listing connected devices, and running an autonomous task. However, autoglm_task references autoglm_execute_action, a tool that is not actually exposed by this server, which could lead an agent to expect or attempt a nonexistent tool.

Naming Consistency2/5

Tool names mix conventions: adb_connect lacks the autoglm_ prefix used by the other two tools, and autoglm_task is a noun rather than a verb-based action name like autoglm_list_adb_devices or adb_connect. The mention of autoglm_execute_action adds another inconsistent naming style not present in the actual tool set.

Tool Count4/5

Three tools is minimal but each covers a necessary stage of the ADB/AutoGLM workflow: connect, list devices, and execute a task. The count feels slightly thin because autoglm_task implies a separate single-action execution tool should exist.

Completeness2/5

The server covers device connection, device listing, and autonomous task execution, but autoglm_task explicitly tells users to use autoglm_execute_action for single known actions, and that tool is missing. This is a significant gap because the intended workflow cannot handle simple direct actions without falling back on the missing tool.

Maintenance

ActivityInactive
ResponsivenessNo issues