Skip to main content
Glama

save_screenshot

Captures a single macOS window and stores it as a numbered screenshot in the shotlog folder with activity, command, and result captions for later Markdown reports.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "save_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNo
nameYes
resultNo
commandNo
activityNo
title_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It does disclose meaningful behavior beyond the name: it captures exactly one window, writes a numbered file into the shotlog folder, and stores a caption consumed later by export_report. It omits macOS screen-recording permission needs, failure behavior, and what the return value contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then three tight bullets that each map to a distinct parameter group. No redundant restatement of the tool name and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter mutation tool with no annotations and no output schema, the description covers the action, target selection, save location, and caption purpose well. The remaining gaps are the return value (filename/path) and any prerequisite system permissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it largely does: all six parameters are addressed, with a concrete example for name, selection semantics for app/title_contains (empty = front-most), and the downstream role of activity/command/result as manifest captions. It stops short of clarifying whether activity/command/result are free text or how they combine into the caption.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Capture ONE macOS window") plus the destination ("shotlog folder") and the numbering behavior. The emphasis on "ONE" implicitly distinguishes it from list_windows/list_screenshots, but no sibling is named explicitly, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete selection guidance for the target window (app / title_contains, empty = front-most), which is actionable. However, it never says when to use this versus list_windows or pull_remote_screenshots, so the when-not/alternative routing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.