Unreal-MCP-Ghost

Overview Schema Source Related Servers Discussions Admin

create_bt_attack_task

Create a Behavior Tree task Blueprint that damages a targeted player, with configurable damage amount and target Blackboard key.

Instructions

Create a Behavior Tree Attack Task Blueprint.

Ch.10: BTTask_DoAttack that deals damage to the player.

TargetActorKey (BlackboardKeySelector) - instance editable
Damage (Float, instance editable, default 0.25 = 25% of player health)
Overrides ReceiveExecute: checks IsValid on target, calls Apply Damage, then calls FinishExecute(Success=true)

Args: name: Task Blueprint name (e.g., "BTTask_DoAttack") damage_variable: Name of the damage float variable default_damage: Default damage amount (0.0-1.0 normalized or raw) target_key_variable: Name of the BlackboardKeySelector variable path: Content browser path

KB: see knowledge_base/04_AI_SYSTEMS.md#overview Example: create_bt_attack_task()

Input Schema

TableJSON Schema

Name	Required	Default
`name`	No	BTTask_DoAttack
`path`	No	/Game/AI
`default_damage`	No
`damage_variable`	No	Damage
`target_key_variable`	No	TargetActorKey

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the generated task's behavior in detail: ReceiveExecute override, IsValid check on target, Apply Damage call, FinishExecute(Success=true), and instance-editable variables with default damage meaning. It stops short of stating creation side effects such as overwrite behavior or whether the asset is compiled.

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 description is well-structured with an intro, bulleted implementation details, a parameter list, a KB reference, and an example invocation. There is minor redundancy between the Damage bullet and the default_damage argument description, but overall it is scannable and free of filler.

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?

The description covers purpose, generated-task behavior, all parameters, defaults, a knowledge-base reference, and an invocation example. With an output schema present, return-value documentation is not required. The main missing context is guidance for choosing this over the many sibling AI/behavior-tree tools.

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 0%, so the Args block compensates by describing all five parameters, including example names and the meaning of default_damage ('0.25 = 25% of player health'). Some entries are terse ('path: Content browser path') and 'normalized or raw' is ambiguous, so it is not a 5.

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?

Opens with a specific verb+resource: 'Create a Behavior Tree Attack Task Blueprint.' It then names the exact task (BTTask_DoAttack) and its purpose ('deals damage to the player'), clearly distinguishing it from generic BT-task or wander-task siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The use case is implied by the name and description, but there is no explicit guidance about when to use this tool versus sibling tools like create_bt_task or create_bt_wander_task. No when-to-use, when-not-to-use, or alternative routing is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server