Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_actors_in_trigger

Read-onlyIdempotent

List actors currently overlapping a specified Unreal Engine trigger volume, sphere, or box without changing the editor world.

Instructions

List the actors that a TriggerBox, TriggerSphere or TriggerVolume in the editor world (not PIE) currently reports as overlapping (AActor::GetOverlappingActors), without changing anything. Returns actor_count and actors [{actor_name, actor_class}]; get_trigger_overlap_count returns only the count.

Returns: { trigger_name, actor_name, actor_class, actors, actor_count }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trigger_nameYesObject name of the trigger actor, such as the actor_name returned by create_trigger; its editor label is not matched.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / trigger_name / description
      Previous value: -"Name of the trigger actor to check"New value: +"Object name of the trigger actor, such as the actor_name returned by create_trigger; its editor label is not matched."
  2. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds meaningfully beyond them with the 'editor world (not PIE)' scope constraint and the overlap semantics (AActor::GetOverlappingActors), plus it discloses the return shape since no output schema exists.

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 main sentence is front-loaded with purpose and scope, and the trailing 'Returns:' line aids the agent in the absence of an output schema. Mild redundancy ('without changing anything' restates the readOnly annotation) costs a little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety and no output schema, the description appropriately supplies the return structure (actor_count, actors array) and the PIE scope caveat. Complete enough to call correctly, though exact failure/empty-result behavior is unstated.

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% and the single parameter is fully documented in the schema (object name, editor label not matched). The description adds no additional parameter-level detail, so baseline 3 applies.

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 (List) and a precise resource (actors overlapping a TriggerBox/TriggerSphere/TriggerVolume), and explicitly names the sibling get_trigger_overlap_count as the count-only variant. An agent can distinguish this from the overlap-count tool without opening any 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?

Provides clear context ('editor world (not PIE)') and routing to the alternative count-only tool. The exclusion of PIE is a genuine when-not condition, though it doesn't cover other edge cases such as what happens if the trigger is unloaded or not found.

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