Skip to main content
Glama

export_render_target

Destructive

Exports a render target asset to an image file on disk as PNG, HDR, or EXR, and verifies the written file for downstream use.

Instructions

Export a render target to an image file on disk: PNG, except an RGBA16f or RGBA32f render target, which writes HDR when filename ends in .hdr and EXR otherwise. exported is measured on disk: the file must exist, hold bytes and have been written by this call. It is false, and the call fails saying why, for a render target without a resource (every render target in a process that cannot render: -nullrhi, a commandlet), an invalid path, a file that cannot be opened for writing, or an image that cannot be read back; an empty file left by a failed export is removed when the call created it.

Returns: { render_target_path: string, output_directory: string, filename: string, file_path: string, exported: bool, file_exists: bool, file_size_bytes: number }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYesOutput file name including extension, e.g. RT_Example.png
output_directoryYesAbsolute directory path to write into, created if missing
render_target_pathYesAsset path of the render target to export

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive=true, idempotent=false): it defines exactly what 'exported' means (file exists, holds bytes, written by this call), enumerates every failure cause (no resource such as -nullrhi/commandlets, invalid path, unwritable file, unreadable image), and discloses cleanup behavior for zero-byte files left by failed exports.

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 core action and format rule are front-loaded, followed by failure semantics and a compact Returns line. The prose is dense and the failure enumeration is long, but each clause carries actionable information rather than filler.

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?

With no output schema, the description compensates by listing the full return object fields, and it covers format selection, success criteria, failure modes and cleanup. An agent has everything needed to call it correctly and interpret the result.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: the filename extension controls the produced format, with RGBA16f/RGBA32f targets writing HDR on .hdr and EXR otherwise. This is format-selection semantics the schema does not convey.

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 ('Export a render target to an image file on disk') and even specifies the output-format branching rules, so the action is unambiguous. It does not name or distinguish itself from sibling export tools (e.g. export_landscape_heightmap, capture_pie_screenshot, render_widget_preview), which keeps it short of a 5.

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?

Usage is implied rather than stated: it reveals that a render target lacking a resource cannot be exported and that the extension selects the format, which lets an agent infer preconditions. However, there is no explicit 'use this when...' guidance nor any reference to alternative export tools.

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