Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_post_process_volume_settings

DestructiveIdempotent

Set enabled, priority, film grain intensity, and motion blur amount for a PostProcessVolume in the UE5 editor as one undo step; only passed fields change.

Instructions

Set enabled, priority, film_grain_intensity and motion_blur_amount of a PostProcessVolume in the editor world as one undo step; only the fields you pass change, and film grain and motion blur also get their bOverride flag so they take effect. The level is not saved. Returns applied_count and applied_fields; other settings use set_post_process_setting.

Returns: { volume_name, applied_count, applied_fields: [string] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledNoWhether the volume is enabled (APostProcessVolume bEnabled).
priorityNoBlend priority among overlapping volumes, a number such as 1; a numeric string is also accepted.
volume_nameYesEditor label of the PostProcessVolume in the editor world; object names are not matched.
motion_blur_amountNoMotion blur strength from 0 to 1 (0 is off), a number; a numeric string is also accepted.
film_grain_intensityNoFilm grain intensity from 0 to 1, a number; a numeric string is also accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.2.0
    • changedInput schema / properties / enabled / description
      Previous value: -"Optional bool (PPV bEnabled)."New value: +"Whether the volume is enabled (APostProcessVolume bEnabled)."
    • changedInput schema / properties / film_grain_intensity / description
      Previous value: -"Optional float."New value: +"Film grain intensity from 0 to 1, a number; a numeric string is also accepted."
    • changedInput schema / properties / film_grain_intensity / type
      Previous value: -"string"New value: +"number"
    • changedInput schema / properties / motion_blur_amount / description
      Previous value: -"Optional float."New value: +"Motion blur strength from 0 to 1 (0 is off), a number; a numeric string is also accepted."
    • changedInput schema / properties / motion_blur_amount / type
      Previous value: -"string"New value: +"number"
    • changedInput schema / properties / priority / description
      Previous value: -"Optional float (PPV Priority)."New value: +"Blend priority among overlapping volumes, a number such as 1; a numeric string is also accepted."
    • changedInput schema / properties / priority / type
      Previous value: -"string"New value: +"number"
    • changedInput schema / properties / volume_name / description
      Previous value: -"Label of the APostProcessVolume."New value: +"Editor label of the PostProcessVolume in the editor world; object names are not matched."
  2. 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 cover the safety profile, but the description adds real behavior beyond them: the operation is a single undo step, only passed fields change (partial update), film grain and motion blur get their bOverride flag set so they take effect, and the level is not saved. These are meaningful traits an agent cannot infer from readOnly/destructive/idempotent hints alone.

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 main action and packs the key caveats into a tight first sentence, then states the return shape. Dense but every clause earns its place; could be marginally cleaner with a line break between behavior and return values.

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?

No output schema exists, and the description supplies the return shape (volume_name, applied_count, applied_fields), the persistence caveat, and the sibling route for unsupported settings. 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.

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3, but the description adds update semantics ('only the fields you pass change') and the override side effect for two of the four optional fields, which clarifies how those parameters behave beyond their schema text.

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 (Set) and resource (fields of a PostProcessVolume in the editor world), and enumerates exactly which fields (enabled, priority, film_grain_intensity, motion_blur_amount). It explicitly names the sibling set_post_process_setting as the tool for other settings, so an agent can disambiguate without opening schemas.

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?

Gives clear context (editor world) and routes the agent to set_post_process_setting for settings this tool does not cover. It doesn't spell out when-not to use it or prerequisites (e.g., volume must exist), so not quite a 5.

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