Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_ability_task

Create an ability task on the primary instance of an ability granted to an editor-world actor, initialized as AwaitingActivation and not activated.

Instructions

Create an ability task on the primary instance of an ability already granted to an editor-world actor; the task is initialized (AwaitingActivation), never activated. task_class is only validated: it always builds the abstract base UAbilityTask, which logs a warning and an ensure.

Returns: { actor_name, ability_class, task_class, instance_name, task_name, added, task_state }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actor_nameYesObject name (not the label) of the editor-world actor, e.g. "BP_Hero_C_1", matched case-insensitively; find_actors_by_name maps labels to names
task_classYesClass path of a UAbilityTask subclass, e.g. "/Script/GameplayAbilities.AbilityTask_WaitDelay"; checked, but not used to build the task
ability_classYesClass path of an ability already granted to the actor, e.g. "/Game/Abilities/GA_Jump.GA_Jump_C"; it must be instanced (have a primary instance)
instance_nameNoName for the new task instance (default "Default")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.0
    • changedInput schema / properties / ability_class / description
      Previous value: -"Gameplay ability class path"New value: +"Class path of an ability already granted to the actor, e.g. \"/Game/Abilities/GA_Jump.GA_Jump_C\"; it must be instanced (have a primary instance)"
    • changedInput schema / properties / actor_name / description
      Previous value: -"Actor label in the level"New value: +"Object name (not the label) of the editor-world actor, e.g. \"BP_Hero_C_1\", matched case-insensitively; find_actors_by_name maps labels to names"
    • changedInput schema / properties / task_class / description
      Previous value: -"UGameplayTask-derived class path"New value: +"Class path of a UAbilityTask subclass, e.g. \"/Script/GameplayAbilities.AbilityTask_WaitDelay\"; checked, but not used to build the task"
  2. First observedv1.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations with a crucial behavioral caveat: the task is initialized as AwaitingActivation and never activated, and task_class is only validated because it always builds the abstract base UAbilityTask (logging a warning and ensure). This warns the agent that the call will not do what its name implies, which is exactly the kind of non-obvious disclosure this dimension rewards.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with zero filler, front-loading the core action and its never-activated behavior, followed by a compact, scannable return-shape line.

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?

Covers preconditions, the surprising initialization behavior, the task_class validation trap, and the returned fields. With no output schema present, the inline Returns block compensates, and annotations already carry the safety profile.

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 four parameters, including the task_class caveat. The Returns block enumerates output fields and adds marginal value, but the description does not extend parameter meaning beyond what the schema provides, so the baseline of 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 precise verb and resource: 'Create an ability task on the primary instance of an ability already granted to an editor-world actor.' It also names the scope (primary instance) and target domain (editor-world actor), which distinguishes it from sibling creation tools like add_state_task or grant_ability.

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?

Clear preconditions are given: the ability must already be granted and instanced (have a primary instance) on the actor. It doesn't name an explicit alternative or a when-not condition, so it falls short of a full routing statement, but the context is unambiguous.

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