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
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
computer_screenshotA

Take a screenshot of the entire virtual screen (all monitors). Returns the image; its pixel space defines the coordinate system for all computer_* tools.

computer_clickA

Click at (x, y) in the LAST screenshot's pixel space. button: left|right|middle, clicks: 1=single, 2=double, 3=triple (select line/paragraph). Outbound gate: a click can press Submit/Send/Delete — needs fresh CONSENT.txt.

computer_typeA

Type text into the focused control via clipboard paste (Arabic-safe). Outbound gate: requires fresh CONSENT.txt (ALLOW line, <10 min old) — typing sends text into an app the user may not see being typed into.

computer_keyB

Press a key or chord: "Return", "ctrl+c", "alt+Tab", "escape". Emphasis: Enter/Return in a chat app SENDS — that needs consent too.

computer_scrollB

Scroll at (x, y). direction: up|down|left|right; amount in wheel notches.

computer_dragB

Drag from (start_x, start_y) to (x, y) — file moves, sliders, selection.

computer_zoomA

Zoom: re-capture a region at higher magnification for reading small text. Coordinates stay in the FULL-screenshot pixel space, never the crop's.

computer_batchA

Run several actions milliseconds apart in ONE call — for timing-critical UI (menus that close on blur, mid-flight buttons). Each item: {"action": , "input": }. Coordinates follow the same screenshot-space rule. Example: [{"action":"left_click","input":{"x":100,"y":50}}, {"action":"key","input":{"key":"Down"}},{"action":"key","input":{"key":"Return"}}]. Returns one result line per action.

computer_waitA

Pause up to 10s between actions (page loads, animations).

computer_mouse_down_upA

Hold or release the LEFT mouse button without moving: action down|up. For press-drag-press-drag-... sequences pyautogui can't do in one call.

computer_hold_keyA

Hold a key for duration seconds then release (e.g. Shift for click-select ranges). One chord only — no '+' combos.

computer_clipboardA

Read or write the system clipboard: action read|write. write copies text; read returns current clipboard content (empty string if none).

computer_open_applicationA

Open an app by name or full .exe path and report what REALLY happened: opened (window appeared) / running-no-window / crashed / nothing-launched. Windows: use start semantics, e.g. "notepad" or "chrome". Waits up to 8s for a visible window.

computer_cursor_positionB

Current mouse cursor position in SCREENSHOT coordinates.

computer_focus_windowA

Bring the first visible top-level window whose title contains title_substring (case-insensitive) to the foreground. Returns the exact title focused or 'not found'. Keyboard actions land there afterward.

computer_read_screenA

OCR the screen. Optional target_title: bring the first window whose title contains it to the foreground FIRST (atomic focus+read — the read cannot miss the target). Returns lines "(x,y) text". Arabic + English.

computer_selfcheckA

Self-heal agent: verify all server subsystems and FIX what it can. Checks heavy imports, audit log writability, capture (non-blank), OCR engine load, screenshots scale sanity, outbound gate state. Returns per-subsystem status + list of automatic repairs applied.

computer_reviewA

Reviewer agent: audits the LAST actions in actions.log against the stated task_description. Flags: actions with external effects that ran, consent-gate bypasses, actions not plausibly related to the task, and error-results. Returns findings + verdict.

computer_capture_monitorA

Screenshot ONE physical monitor (1..N). computer_screenshot captures the whole virtual desktop; use this to zoom on one display on multi-monitor setups. List displays with computer_display_overview.

computer_display_overviewA

List all physical monitors with resolution and virtual-desktop position. Returns JSON array: index, left, top, width, height. Use before computer_capture_monitor to pick the right display index.

computer_teach_stepA

Teach mode (stub scaffold): records that the HUMAN wants to demo an action for the agent to repeat. Returns guidance text. Full playback recording is planned; use computer_batch scripts for repeatable sequences today.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 21 tools

Disambiguation5/5

Each tool has a clearly distinct role: input actions (click, type, key, scroll, drag), screen inspection (screenshot, zoom, read_screen), display management, and meta/system tools are well separated. The several capture-related tools are distinguished by scope (whole virtual screen vs one monitor vs region zoom vs display listing) and their descriptions make the intended usage explicit.

Naming Consistency5/5

All tools use a consistent `computer_` prefix with snake_case names, and there is no mixing of camelCase or unrelated conventions. Some names are noun-like (`computer_screenshot`, `computer_clipboard`) rather than pure verb_noun, but the pattern is predictable throughout.

Tool Count4/5

At 21 tools, the server is slightly above the typical well-scoped range, but most tools earn their place by covering distinct GUI automation concerns. A few meta/extras such as `computer_teach_step` feel less essential, but the overall count is reasonable for full computer-use coverage.

Completeness4/5

The surface covers the core GUI lifecycle well: screen capture, mouse/keyboard input, clipboard, application launch, window focus, OCR, batch actions, and safety/review checks. Minor gaps remain, such as no explicit window listing, minimize/close/resize operations, or standalone right-button hold/release, but agents can work around these in most cases.

Maintenance

ActivityMaintained
ResponsivenessOutdated data