Skip to main content
Glama

take_screenshot

Capture screenshots from Windows applications while working in WSL. Target specific monitors, windows by title or process, and receive optimized images directly or save to custom paths.

Instructions

WSLSnapIt: Smart screenshot capture for WSL. Capture monitors, windows by title/process, with direct image return and auto-compression.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameNoFilename for the screenshot (default: screenshot.png). Ignored when returnDirect is true.screenshot.png
monitorNoWhich monitor to capture: "all" (default), "primary", or monitor number (1, 2, etc.)all
windowTitleNoCapture a specific window by its title (partial match supported). If multiple windows match, you'll get a list to choose from.
windowIndexNoWhen multiple windows match the title, specify which one to capture (1 for first, 2 for second, etc.). Default: 1
processNameNoCapture a specific window by process name (e.g., "notepad.exe" or just "notepad")
folderNoCustom folder path to save the screenshot (supports both WSL and Windows paths). Ignored when returnDirect is true.
returnDirectNoIf true, returns the image directly to Claude without saving to disk. Large images will be automatically resized and compressed to fit within 1MB limit.
qualityNoJPEG quality (1-100). Only applies when returnDirect is true. Default: 80. Will be automatically reduced if needed.
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: 'direct image return' (output behavior), 'auto-compression' (processing behavior), and 'smart' capture with title/process matching. It doesn't mention potential side effects like screen flashing or permissions needed, but covers the core functionality adequately for a tool with no annotations.

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?

The description is perfectly concise - a single sentence that packs essential information: tool identity (WSLSnapIt), purpose (smart screenshot capture), context (for WSL), key features (capture options), and behavioral traits (direct return, auto-compression). Every word earns its place with zero redundancy.

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 tool with 8 parameters, 100% schema coverage, and no output schema, the description provides good contextual completeness. It covers the tool's purpose, key behaviors, and context. The main gap is lack of output format details (what exactly is returned when returnDirect is true/false), but given the schema's thorough parameter documentation, this is a minor omission.

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

Parameters3/5

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

With 100% schema description coverage, the input schema already documents all 8 parameters thoroughly. The description adds minimal parameter semantics beyond the schema - it mentions 'monitors, windows by title/process' which aligns with parameters but doesn't provide additional context. This meets the baseline of 3 when schema coverage is high.

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?

The description clearly states the specific action ('capture'), target ('screenshot'), and context ('for WSL'). It distinguishes itself from the only sibling tool 'read_clipboard' by focusing on image capture rather than clipboard operations. The description includes key capabilities like capturing monitors/windows and direct image return with compression.

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

Usage Guidelines4/5

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

The description provides clear context about when to use this tool ('smart screenshot capture for WSL') and implies usage scenarios through its feature list. However, it doesn't explicitly state when NOT to use it or mention alternatives to this specific screenshot tool. The sibling tool 'read_clipboard' is unrelated, so no explicit comparison is needed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/peterparker57/WSLSnapit-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server