Peggle AI MCP Server
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 |
|---|---|
| capture_screenB | Captures a screenshot of the primary monitor and returns it as a base64 encoded string. |
| click_atB | Moves the mouse to the specified coordinates and performs a left click. |
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 2 tools
The two tools have completely distinct purposes: one captures visual data from the screen, while the other performs a mouse interaction at specific coordinates. There is no overlap in functionality, making it impossible to confuse them.
Both tools follow a consistent verb_noun pattern with snake_case naming: capture_screen and click_at. The naming is clear, predictable, and adheres to the same convention throughout.
With only two tools, the server feels thin for a general-purpose automation or interaction domain like screen capture and mouse control. Key operations such as keyboard input, drag-and-drop, or region-specific screenshots are missing, limiting the scope significantly.
For a server implied to handle desktop automation or interaction (based on screen capture and mouse click), there are significant gaps. Missing tools include keyboard input, mouse movement without clicking, drag operations, and more advanced screen interactions, which will likely cause agent failures in broader automation tasks.