ElfdeckAI
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 |
|---|---|
| key_tapC | Tap a key on the virtual keyboard. |
| key_downA | Hold a key down (release with key_up, or key_release for all). |
| key_upC | Release a held key. |
| key_releaseA | Release every held key at once — the unstick button, for when a caller died mid-hold or state is unknown. |
| pad_pressC | Tap a gamepad button or D-pad direction. In Steam Deck Gaming Mode, if the game ignores the pad, ElfPad is not Player 1: open Steam > Controller Settings > Reorder Controllers while the game runs and move the non-Deck controller to the top. |
| pad_downB | Hold a gamepad button or D-pad direction down. In Steam Deck Gaming Mode, if the game ignores the pad, ElfPad is not Player 1: open Steam > Controller Settings > Reorder Controllers while the game runs and move the non-Deck controller to the top. |
| pad_upB | Release a held gamepad button or D-pad direction. |
| pad_stickA | Move an analog stick (x/y in percent, -100..100). Without hold_ms the stick stays; with it, it recenters after. |
| pad_triggerB | Set an analog trigger (percent 0..100). Without hold_ms it stays; with it, it releases after. |
| pad_centerB | Return sticks, triggers and D-pad to neutral. |
| pad_resetB | Release every button and recenter everything. |
| mouse_moveA | Move the pointer relatively by (dx, dy). Pointer acceleration applies, so prefer mouse_move_to for targeting. Optional glide_ms spreads the move over time. |
| mouse_move_toA | Move the pointer to (x, y), in the pixel coordinates of the most recent screenshot (0,0 is its top-left corner). Takes a screenshot first if none has been taken yet. |
| mouse_click_atA | Move the pointer to (x, y) in the pixel coordinates of the most recent screenshot, then click (left by default). |
| mouse_clickC | Click a mouse button at the pointer's current position. |
| mouse_downB | Hold a mouse button down (start a drag). |
| mouse_upB | Release a mouse button (drop the drag). |
| mouse_scrollC | Scroll the wheel: positive clicks up, negative down. |
| mouse_hscrollB | Scroll horizontally: positive clicks right. |
| mouse_releaseA | Release every held mouse button at once — the unstick button, for when a caller died mid-drag. |
| screenshotA | Capture the screen of the machine this server runs on (e.g. a Steam Deck in Desktop Mode) and return it as a PNG image, scaled down if the screen is large. mouse_move_to and mouse_click_at take coordinates in this image's pixels. Requires a graphical session on the server's machine. |
| waitA | Wait before the next tool call, in milliseconds. Use it for timing between inputs: queued taps land back-to-back with essentially no gap, and a frame-polled game can merge them into one hold. Bounded like every tap. |
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 22 tools
Tools are mostly distinct by device and action, with clear separation between tap, hold, release, and safety-release operations. A few pairs (pad_center vs pad_reset, mouse_up vs mouse_release) overlap conceptually, but the descriptions help disambiguate them.
Names predominantly follow a snake_case device_action pattern (key_tap, pad_press, mouse_click), which is predictable. Minor deviations like mouse_move_to/mouse_click_at suffix forms and single-word screenshot/wait, plus the abbreviation hscroll, keep it from perfect consistency.
At 22 tools, the surface is on the heavy side for a general MCP server, and several granular hold/release/reset variants could feel excessive. Each tool does correspond to a real input primitive, but the count is borderline per typical scoping guidance.
The core input surface is comprehensive: keyboard, mouse, and gamepad tap/hold/release, analog sticks and triggers, recentering, screenshots, and timing. Minor gaps like text-entry (type_string) and multi-touch gestures exist, but there are no major workflow dead ends.