Unlimited Agent
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execA | Run an arbitrary PowerShell command on this Windows PC. Use for local development, package installation, system configuration, services, processes, and tasks not covered by a more specific tool. Verify changes afterward. |
| read_fileA | Read any local file accessible to the current Windows user. Use utf8 for text and base64 for binary files. |
| write_fileA | Create, overwrite, or append to any local file. Create missing parent folders when requested, then verify important writes with read_file or path_info. |
| edit_fileA | Replace exact text in a UTF-8 local file. Use for focused edits that preserve the rest of the file. |
| list_directoryA | List files and folders with type, size, and modified time. Use before guessing paths or choosing files to edit. |
| path_infoA | Check whether a local path exists and return detailed file, folder, or symbolic-link metadata. |
| search_filesA | Fast local search using ripgrep. Search file names or text contents before reading large directory trees. |
| file_operationA | Copy, move, delete, or create local files and folders. Use exact resolved targets and verify consequential operations afterward. |
| http_requestB | Call an HTTP/HTTPS URL from this PC or download the response to a local file. Does not inherit OpenAI or tunnel credentials. |
| screenshotA | Capture the primary display or full virtual desktop as a PNG image. Use before and after graphical actions to locate controls and verify outcomes. |
| list_windowsA | List top-level Windows desktop windows with title, process ID, handle, position, size, and minimized state. Use to target window_control reliably. |
| window_controlA | Focus, minimize, maximize, restore, or close a desktop window by the handle returned from list_windows. |
| computer_inputA | Send mouse, keyboard, text, scrolling, and wait actions to the interactive Windows desktop. Take a screenshot first, focus the target window, act, then screenshot again to verify. |
| clipboardA | Read text from or write text to the interactive Windows clipboard. |
| open_urlA | Open an HTTP/HTTPS URL in Google Chrome using a profile belonging to the current Windows user. |
| browser_controlA | Open a URL or send navigation/tab shortcuts to the focused Chrome window. For reliable GUI browsing, list windows, focus Chrome, act, then capture a screenshot. |
| launch_programB | Launch a local executable or script with arguments, optionally visible. Use list_windows and screenshot after launching GUI applications. |
| start_jobA | Start a long-running PowerShell command in the background with persistent stdout/stderr logs. Poll with job_status instead of waiting in exec. |
| job_statusA | List background jobs or inspect one job with running state and recent stdout/stderr. Poll until completion and verify the resulting files or application state. |
| stop_jobA | Force-stop a background job and its child process tree by job ID. |
| system_infoA | Return local Windows, CPU, memory, user, host, runtime, and server capability information without changing the PC. |
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 21 tools
Each tool has a clearly distinct purpose: file operations (read, write, edit, list, search, path, copy/move/delete) are separate from process execution (exec, launch, background jobs), GUI automation (screenshot, list/control windows, input, clipboard, open_url, browser_control), web requests, and system info. No two tools could be easily confused.
All tool names follow a consistent snake_case verb_noun or verb_phrase pattern (e.g., read_file, list_windows, start_job, system_info). No mixing of styles or vague verbs, making the API predictable and intuitive.
With 21 tools, the set is on the higher end of the typical range but still well-scoped for a comprehensive Windows automation server. Each tool earns its place; no obvious bloat. Slight overage compared to the ideal 3-15 range, but justified by the breadth of capabilities.
The tool surface covers file CRUD, directory listing, search, file operations, arbitrary command execution, GUI interaction (screenshot, window control, mouse/keyboard, clipboard, browser control), web requests, background job management, and system info. No significant gaps for the stated purpose of local Windows automation.