Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_ai_perception_sense

Idempotent

Configure sight or hearing senses on a Blueprint's AIPerceptionComponent template and save the asset. Updates existing sense configs in place so AI perception settings persist with the Blueprint.

Instructions

Configure a sight or hearing sense on an AIPerceptionComponent TEMPLATE of a Blueprint, creating the config as an Instanced subobject of the template so it persists with the asset, and saving the package. Idempotent: ConfigureSense dedups by config class, so re-calling with the same sense_type UPDATES the existing config in place instead of stacking a second one. Only "sight" and "hearing" are supported (no damage, touch or team senses). It authors the TEMPLATE only -- whether the AI actually perceives anything is a live-PIE question this cannot answer; read the authored result back with get_ai_perception_senses.

Returns: { blueprint_name, component_name, sense_type, config_class, , note }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoOptional. This command is REFUSED while a Play-in-Editor session is running: it either compiles a Blueprint (the reinstancer can retain a world, and CheckForWorldGCLeaks is Fatal -- it KILLS the editor) or writes to disk (Editor.AllowSavingAssetsDuringPIE=0 makes the engine refuse the write, so it would report success without writing a byte). Stop PIE and retry instead; force=true runs it anyway, at your own risk.
dominantNoOptional bool; if true, sets this sense as the component's dominant sense
sense_typeYes"sight" or "hearing"
sight_radiusNo(sight) Maximum sight distance, cm (ClampMin 0)
hearing_rangeNo(hearing) Hearing range, cm (ClampMin 0)
blueprint_nameNoName of the blueprint owning the component
blueprint_pathNoAlias of `blueprint_name` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `blueprint_name`.
component_nameYesName of the AIPerceptionComponent SCS node
detect_enemiesNoOptional bool affiliation filter
detect_neutralsNoOptional bool affiliation filter
detect_friendliesNoOptional bool affiliation filter
lose_sight_radiusNo(sight) Distance to keep seeing an already-seen target, cm (ClampMin 0)
peripheral_vision_angleNo(sight) Peripheral vision half-angle, degrees (Clamp 0..180)

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?

Beyond the annotations (which already declare idempotent=true, destructive=false, readOnly=false), the description discloses that the config is created as an Instanced subobject that persists with the asset, saves the package, and dedups by config class so re-calls update in place. It also adds the crucial template-only caveat: it authors the asset but cannot answer whether the AI perceives anything in live PIE.

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 each sentence adds a distinct fact (persistence, idempotency, supported types, template-only scope, return shape). Slightly dense but nothing is wasted.

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 supplies the return shape ({blueprint_name, component_name, sense_type, config_class, <sense fields>, note}), and it covers the key limitation an agent must know before authoring perception. Complete for this mutation tool.

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 all 13 parameters including the force/PIE-refusal param. The description reinforces only the sense_type constraint (sight/hearing). This is the correct baseline: the schema carries the parameter burden.

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 description opens with a specific verb and resource: configuring a sight or hearing sense on an AIPerceptionComponent template of a Blueprint. It clearly distinguishes this authoring tool from the read-back sibling get_ai_perception_senses and implies difference from configure_ai_sight_radius/add_ai_stimuli_source. An agent knows exactly what asset state this mutates.

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?

It states the supported sense types (sight/hearing only), explains idempotent re-call behavior, and explicitly points to get_ai_perception_senses for reading the result back. It does not, however, explicitly position itself against sibling authoring tools like configure_ai_sight_radius, so the alternative-selection guidance is incomplete.

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