Skip to main content
Glama

sassy_screenshot

Idempotent

Capture a PNG screenshot of the current screen, a monitor, or a selected region, save it to a validated path, and return the file path and pixel dimensions for inspecting desktop state.

Instructions

Read-only with respect to the desktop; writes an image file. Saves a PNG screenshot of the screen and returns its path and pixel dimensions. path defaults to ~/sassymcp_screenshot.png; region is an 'x,y,w,h' string that takes precedence over monitor (a malformed region returns an explicit error instead of falling back to a full screenshot); monitor defaults to -1 (all monitors), 0 for primary, 1+ for others. The save path must pass validation and must not be a protected location. Use it to see the current screen state, especially before or after sassy_click/sassy_type_text; pair with sassy_screen_info for multi-monitor region math. Requires a GUI session; on headless hosts it returns an error.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
pathNo
regionNo
monitorNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

The opening line reconciles the apparent tension with readOnlyHint=false by scoping the read-only claim to the desktop while disclosing the file write, which the annotations alone would not explain. Beyond that it adds behavior annotations do not carry: path validation against protected locations, a malformed region returning an explicit error instead of silently degrading to a full screenshot, and a hard headless-session failure mode.

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

Conciseness4/5

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

The load-bearing fact (read-only on desktop, writes a file) is front-loaded and no sentence is filler. It is dense, semicolon-chained prose though; splitting the parameter defaults into a short list would improve scannability without lengthening it much.

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

Completeness5/5

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

Return values are covered by the output schema and the description only needs to flag that a path and dimensions come back, which it does. With defaults, precedence rules, error semantics, and the GUI precondition all stated, an agent has everything needed to call this correctly on the first attempt.

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

Parameters5/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 carry the parameters and it does: it supplies the real default path (~/sassymcp_screenshot.png, not the empty schema default), the 'x,y,w,h' region format with its precedence over monitor, and the full monitor encoding (-1 all, 0 primary, 1+ others). It also documents a validation constraint on path that appears nowhere in the schema.

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

Purpose5/5

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

"Saves a PNG screenshot of the screen and returns its path and pixel dimensions" is a specific verb+resource+output statement. It also distinguishes itself from the nearest sibling by telling the agent to pair with sassy_screen_info for region math, so the agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ("to see the current screen state, especially before or after sassy_click/sassy_type_text"), an explicit companion tool (sassy_screen_info) for the multi-monitor case, and an explicit environment precondition ("Requires a GUI session; on headless hosts it returns an error"). This is the full when/with-what/under-what-condition triad.

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

Deploy Server

Other Tools