Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_camera_post_process

DestructiveIdempotent

Applies post-process settings to a camera actor by setting supplied fields and enabling their override flags, forcing blend weight above zero and marking render state dirty.

Instructions

Write PostProcessSettings on a camera actor's camera component (plain or cine) by field presence, turning on each field's bOverride_* companion so it takes effect (like a PostProcess Volume). Supplied fields only; scalars are numbers, color-grading wheels are [R,G,B,master] arrays, scene_color_tint is [R,G,B,A]. Absolute + idempotent. Forces PostProcessBlendWeight>0 and marks the render state dirty.

Returns: { actor_name: string, applied_count: int, applied: object (field -> value read back), post_process_blend_weight: number, success: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actor_nameYesName or label of the camera actor to modify.
color_gainNoOptional color gain wheel [R,G,B,master] (array).
white_tempNoOptional white balance temperature (number).
white_tintNoOptional white balance tint (number).
color_gammaNoOptional color gamma wheel [R,G,B,master] (array).
color_offsetNoOptional color offset wheel [R,G,B,master] (array).
exposure_biasNoOptional auto-exposure bias / EV compensation (number).
color_contrastNoOptional color contrast wheel [R,G,B,master] (array).
bloom_intensityNoOptional bloom intensity (number).
bloom_thresholdNoOptional bloom threshold (number).
color_saturationNoOptional color saturation wheel [R,G,B,master] (array).
scene_color_tintNoOptional scene color tint [R,G,B,A] (array).
exposure_speed_upNoOptional auto-exposure adaptation speed up (number).
vignette_intensityNoOptional vignette intensity 0..1 (number).
exposure_speed_downNoOptional auto-exposure adaptation speed down (number).
depth_of_field_fstopNoOptional depth-of-field f-stop (number).
film_grain_intensityNoOptional film grain intensity 0..1 (number).
exposure_max_brightnessNoOptional auto-exposure maximum brightness (number).
exposure_min_brightnessNoOptional auto-exposure minimum brightness (number).
ambient_occlusion_radiusNoOptional ambient occlusion radius (number).
ambient_occlusion_intensityNoOptional ambient occlusion intensity 0..1 (number).
depth_of_field_focal_distanceNoOptional depth-of-field focal distance in cm (number).
chromatic_aberration_intensityNoOptional chromatic aberration / scene fringe intensity (number).
chromatic_aberration_start_offsetNoOptional chromatic aberration start offset 0..1 (number).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: it explains the bOverride_* companion mechanism, that only supplied fields apply, that it is absolute/idempotent, and that it forces PostProcessBlendWeight>0 and marks the render state dirty. This is exactly the side-effect disclosure a mutation tool needs, and idempotency matches the idempotentHint.

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?

Front-loads the core action and side effects in one dense sentence, then a separate Returns block. Most sentences earn their place; the format restatement slightly duplicates the schema.

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?

For a 24-parameter mutation tool with no output schema, the description covers what it modifies, field formats, override behavior, idempotency, side effects, and an inline return shape. Nothing an agent needs to invoke it correctly appears to be missing.

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 100%, so the schema already documents each of the 24 fields, including the [R,G,B,master] and [R,G,B,A] array formats. The description restates those format rules and the bOverride mechanism but adds no per-parameter meaning beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb and resource ('Write PostProcessSettings on a camera actor's camera component') and scopes it to plain or cine components. An agent can distinguish this from sibling volume/setting tools like set_post_process_volume_settings 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 Guidelines4/5

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

The description gives clear context: it targets a camera actor's camera component and behaves 'like a PostProcess Volume', which helps orient usage. However, it names no explicit alternative (e.g. set_post_process_setting) nor any when-not condition, so routing is inferred rather than stated.

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