Fetch an actor's outliner folder path in Unreal Engine 5, so AI agents can check where actors are grouped in the world outliner.
Read an actor's outliner folder path (reader twin of set_actor_folder)
Returns: { actor_name: string, folder_path: string }
| Name | Required | Description | Default |
|---|---|---|---|
| actor_name | Yes | Actor name or label in the world outliner |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds value by disclosing the return shape ({ actor_name, folder_path }), which matters 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two compact lines with zero waste; the purpose is front-loaded and the return contract immediately follows. Every segment earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter reader with no output schema, the description supplies the one thing structured fields do not: the return payload shape. It is essentially complete, with only minor room for edge-case notes (e.g., what happens if the actor has no folder).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter with 100% schema description coverage, so the schema already documents actor_name as 'Actor name or label in the world outliner'. The description adds no syntax or format detail beyond what the schema provides, making the baseline 3 correct.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Read') and resource ('an actor's outliner folder path'), and explicitly frames itself as the 'reader twin of set_actor_folder', so an agent can place it against the sibling 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The parenthetical 'reader twin of set_actor_folder' implies this is the read counterpart to a write, giving some orientation. However it never states when to prefer this over the read tools generally, nor any prerequisites or exclusions, leaving usage only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.