ScreenShotTool MCP
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| launch_appA | Launch a Windows .exe and optionally wait for its first visible window. Use noActivate to prevent the window from stealing focus. |
| list_windowsA | List visible top-level Windows desktop windows, optionally filtered by pid, process name, or title substring. |
| capture_windowA | Capture a window by hwnd, pid, process name, or title substring. captureMethod 'print' works on occluded/minimized windows. noActivate avoids stealing focus. |
| capture_screen_regionB | Capture a screen-space rectangle in physical pixels. |
| click_windowA | Post mouse click messages to a window-relative coordinate without moving the physical cursor. |
| click_menu_itemA | Invoke a native Windows menu item by menu path without moving the physical cursor or using keyboard shortcuts. |
| move_mouse_windowA | Post a WM_MOUSEMOVE message to a window-relative coordinate without moving the physical cursor, useful for hover states before taking a screenshot. |
| close_appA | Terminate a process and its descendants via taskkill /T /F. |
| type_textA | Type text into a window via SendInput Unicode. noActivate uses PostMessage WM_CHAR so the target window doesn't need focus. |
| send_keyB | Send a keystroke with optional modifiers. noActivate uses PostMessage WM_KEYDOWN/WM_KEYUP so the target window doesn't need focus. |
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 10 tools
All tools have clearly distinct purposes: capturing, listing, launching/closing apps, and various input actions (click, menu click, move mouse, send key, type text). Even the two input tools (send_key vs type_text) are differentiated by keystrokes vs text input.
All tools follow a consistent verb_noun pattern with lowercase and underscores (e.g., capture_screen_region, click_window, send_key). No mixing of camelCase or other conventions.
10 tools cover the main actions for screen capture and window interaction (capture, list, launch, close, click, menu click, keyboard input, mouse move). Not too few or too many for the scope.
Covers core capture and interaction needs, but lacks explicit full-screen capture, monitor enumeration, mouse scrolling, or window sizing. These are minor omissions for a screenshot-focused toolset.