Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Capture Screen To File

capture_screen_to_file

Capture the screen or a defined region and save it as a PNG file for documentation, debugging, or review.

Instructions

Save a screenshot to a PNG file. Region optional (all four of x/y/width/height required to be used).

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": {
      "path": "<path>"
    },
    "name": "capture_screen_to_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
pathYes
widthNo
heightNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 the output format (PNG) and the real behavioral rule that all four region parameters must be supplied together. It omits other mutation-relevant behavior such as whether an existing file at 'path' is overwritten, whether the parent directory must exist, and any screen-capture permission requirements.

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?

Two short sentences, zero filler, with the primary action stated first and the conditional constraint immediately after. Nothing is padded or redundant.

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

Completeness3/5

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

An output schema exists, so return values and file metadata need not be explained. However, for a write-to-disk tool with no annotations and five undocumented schema parameters, the definition should also address overwrite behavior and coordinate units to be genuinely complete.

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?

Schema description coverage is 0%, so the description must compensate, and it does explain the most consequential semantics: region is optional but all of x/y/width/height are required together. It leaves 'path' self-evident but never states whether coordinates are in pixels, whether they are relative to the full desktop, or how multi-monitor setups are treated.

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 outcome: 'Save a screenshot to a PNG file,' which tells an agent this produces a file on disk rather than an inline image. It does not explicitly name or contrast with siblings like capture_screen or capture_screen_region, so the agent must infer that file output is the differentiator.

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?

The phrase 'Save a screenshot to a PNG file' implies the use case (persisting a capture) and the region clause gives conditional guidance for partial captures. There is no explicit when-to-use versus when-not, and no alternative tool is named for the full-screen-inline case.

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