computeruse
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| computeruse_helpA | Read this first. Explains how external AI agents should use ComputerUse MCP tools, including observe -> one action -> verify workflow, coordinate rules, safety rules, and action schema. |
| computeruse_start_sessionA | Start a tracked ComputerUse session for an external agent task. This creates/overwrites sessions/active_session.json and adds a run row to SQLite history. |
| computeruse_observeA | Capture the current screen and optionally visible UI Automation elements. Returns structured screen dimensions, element IDs, and an MCP image. Use this before each click/type decision. |
| computeruse_execute_stepA | Execute exactly one ComputerUse action using the latest observation for coordinate and element mapping. Supports dry_run validation and optional verification screenshot. Call observe or inspect verification before the next step. |
| computeruse_finish_sessionB | Finish the active MCP-tracked session as done, failed, or cancelled with a summary. |
| computeruse_list_historyA | List recent tracked ComputerUse runs from SQLite history. This is read-only and does not replay actions. |
| computeruse_get_history_sessionA | Get one tracked run with all recorded step summaries from SQLite history. This is read-only. |
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 7 tools
Each tool maps to a distinct phase of the ComputerUse workflow: help, session lifecycle, observation, action execution, and history retrieval. Even list_history and get_history_session are clearly separated as list-versus-detail operations.
All tools share a consistent computeruse_ prefix and use snake_case. Most follow a verb_noun pattern like start_session and execute_step, though observe and help are slightly less uniform.
Seven tools is a well-scoped set for a computer-use agent server. Each tool supports a necessary part of the observe-act-verify workflow without redundancy.
The tool surface covers the full agent lifecycle: onboarding help, starting a session, observing state, executing steps, finishing sessions, and reviewing history. There are no obvious dead ends in the core workflow.