Skip to main content
Glama

high_res_screenshot

Destructive

Capture a high-resolution supersampled screenshot of the Unreal Editor viewport or active PIE session and write it synchronously to a PNG for verification.

Instructions

Capture a high-resolution (supersampled) screenshot and write it to a PNG SYNCHRONOUSLY. Prefers the Play-In-Editor game view when PIE is active (captured_pie=true); otherwise the active editor viewport. Drives FViewport::TakeHighResScreenShot() + FViewport::Draw(), which renders at resolution_multiplier x the viewport size and blocks (via ProcessScreenShots) until the file is on disk. The "HighResShot" exec path defers the write to the next render frame, which never runs headless, so it writes nothing. Requires a real RHI (errors honestly under -nullrhi) and a live viewport. Note: the supersampled path re-renders the scene, so the UMG/Slate HUD is NOT included; use capture_pie_screenshot for a HUD-inclusive PIE shot.

Returns: { written: bool, file_path: string, resolution_multiplier: int, width: int, height: int, captured_pie: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameNoOptional output path; a bare name lands under <ProjectSaved>/Screenshots/, an absolute path is respected verbatim. ".png" is appended if missing. Defaults to a timestamped name.
resolution_multiplierNoResolution multiplier (clamped 1..16, default 2).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare destructive/not-readonly; the description adds much more: it blocks synchronously until the file is on disk, it re-renders the scene so the UMG/Slate HUD is excluded, it errors honestly under -nullrhi, and it explains why the deferred exec path writes nothing headless. This is rich behavioral context beyond the structured hints.

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?

Purpose is front-loaded and every caveat is relevant, but the description is quite long and includes implementation internals (FViewport::TakeHighResScreenShot() + Draw(), ProcessScreenShots) that an agent selecting a tool does not strictly need. Efficient but slightly over-detailed.

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?

There is no output schema, yet the description supplies the full return shape (written, file_path, resolution_multiplier, width, height, captured_pie). Combined with the caveats and preconditions, an agent has everything needed to call it correctly.

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 coverage is 100%, so filename and resolution_multiplier are already fully documented with defaults and clamping. The description adds only marginal meaning ('resolution_multiplier x the viewport size'), so the baseline 3 is appropriate when the schema does the heavy lifting.

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 first sentence gives a specific verb+resource ('Capture a high-resolution (supersampled) screenshot and write it to a PNG'), and it explicitly distinguishes itself from the sibling capture_pie_screenshot and from the 'HighResShot' exec path. An agent can tell exactly what this produces without opening the 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?

It states when the tool prefers PIE vs the editor viewport, names the alternative for HUD-inclusive PIE shots, and lists the preconditions (real RHI, live viewport) plus the nullrhi failure mode. This is explicit when/when-not/alternative guidance.

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