autoglm-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTOGLM_MODEL | No | Model to use | autoglm-phone |
| AUTOGLM_API_KEY | Yes | Your AutoGLM API key | |
| AUTOGLM_API_URL | No | Base URL for AutoGLM API | https://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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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:
Examples:
Prerequisites:
|
| 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:
Connection Types:
Examples:
Error Handling:
|
| 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:
How it works:
Examples:
Error Handling:
|
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 3 tools
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.
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.
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.
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.