Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SHOTLOG_DIRNoDirectory where screenshots, manifest.json and report.md are saved./data

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_windowsA

List visible windows (id, app, title, size). The first one is the front-most.

save_screenshotA

Capture ONE macOS window and save it numbered in the shotlog folder.

- name: short slug, e.g. "step1_install".
- app / title_contains: pick the window (e.g. app="Terminal"). Empty = front-most window.
- activity / command / result: caption stored in the manifest and used by export_report.
pull_remote_screenshotsA

Fetch new PNG screenshots from another machine over SCP (e.g. a Windows laptop where Win+PrtScn saves to Pictures\Screenshots) and add them to the log. Requires an SSH server on that machine and key-based auth (no password prompt).

update_captionC

Fill in or fix the caption (activity, command, result) of a saved screenshot.

list_screenshotsA

List every logged screenshot with its caption, in order.

export_reportC

Write report.md in the shotlog folder: every screenshot with its caption, in order. Convert it to PDF/DOCX with any tool (e.g. pandoc).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation4/5

Each tool maps to a distinct action on a distinct object (live windows, saved screenshots, captions, remote fetch, report export). The only mild overlap is list_windows vs list_screenshots, whose names look similar but whose descriptions clearly separate live window enumeration from logged-entry listing.

Naming Consistency5/5

All six tools follow a strict snake_case verb_noun pattern (list_windows, save_screenshot, update_caption, pull_remote_screenshots, list_screenshots, export_report). The verbs (list, save, update, pull, export) accurately signal each operation's semantics.

Tool Count5/5

Six tools is well-scoped for a screenshot-logging workflow, covering capture, remote ingest, listing, captioning, and export without redundancy. Every tool earns its place, and there is no bloat.

Completeness4/5

The surface covers the core lifecycle: capture (save_screenshot/pull_remote_screenshots), read (list_screenshots/list_windows), edit captions, and export. The notable gaps are a delete/remove operation for logged screenshots and any get-single-screenshot or reorder tool, which agents would otherwise have to work around manually.

Maintenance

ActivityMaintained
ResponsivenessOutdated data