SnapStack Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNAPSTACK_DIR | No | Stack folder path. | ~/.snapstack |
| SNAPSTACK_PORT | No | Listening port (always on 127.0.0.1). | 4123 |
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 |
|---|---|
| get_screenshotsA | List the pending browser screenshots as a manifest — NO image data. The stack is the local folder where the SnapStack browser extension pushes captures. Each entry has a stable two-digit "number", the absolute local "path", "width"/"height", and metadata (url, title, capturedAt, format, bytes). Read the file at "path" yourself only if you need the pixels. This tool does NOT delete anything — use clear_screenshots to remove captures. Pass "numbers" to list only specific captures (e.g. [1] or [1,3]); omit to list them all. |
| clear_screenshotsA | Delete pending screenshots from the stack. Pass "numbers" to delete only specific captures (e.g. [1] or [2,3]); omit to clear the whole stack. Once the stack is empty, numbering restarts at 01. |
| count_screenshotsA | Return the number of pending screenshots in the stack without retrieving or clearing them. |
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 3 tools
Each tool has a distinct purpose: clearing, counting, and listing screenshots. There is no overlap in functionality, and the descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case (clear_screenshots, count_screenshots, get_screenshots), making them predictable and easy to understand.
Three tools are appropriate for the narrow domain of managing a screenshot stack. Each tool provides essential functionality without redundancy or unnecessary complexity.
The tool set covers the core operations needed to manage pending screenshots: listing metadata, counting, and clearing. Since capture is handled externally by a browser extension, the server's surface is complete.