Skip to main content
Glama
Flux-Point-Studios

Unreal Engine MCP Server

manage_gas

Create and configure Unreal Engine Gameplay Ability System assets: abilities, effects, attribute sets, and gameplay cues.

Instructions

Create Gameplay Abilities, Effects, Attribute Sets, and Gameplay Cues for ability systems.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the asset to create.
pathNoDirectory path for asset creation.
saveNoSave the asset(s) after the operation.
actionYesGAS action to perform.
cueTagNoGameplay Cue tag (e.g., GameplayCue.Damage.Fire).
periodNoPeriod for periodic effects.
cuePathNoPath to Gameplay Cue asset.
cueTypeNoType of gameplay cue notify.
tagNameNoName of the tag.
durationNoDuration in seconds.
maxValueNoMaximum value for clamping.
minValueNoMinimum value for clamping.
taskTypeNoType of ability task to add.
aoeRadiusNoArea of effect radius.
assetPathNoAsset path (e.g., /Game/Path/Asset).
baseValueNoBase value for attribute.
clampModeNoAttribute clamping mode.
decalPathNoPath to decal material.
soundPathNoSound asset path.
effectPathNoPath to effect asset.
ownerActorNoOwner actor class for ASC.
abilityPathNoPath to ability asset.
abilityTagsNoGameplay tags for this ability.
avatarActorNoAvatar actor class for ASC.
coefficientNoCoefficient for attribute-based calculation.
grantedTagsNoTags granted while effect is active.
parentClassNoPath or name of the parent class.
removalTagsNoTags that cause effect removal.
targetRangeNoMaximum targeting range.
triggerTypeNoWhen the cue triggers.
cooldownTagsNoTags applied during cooldown.
durationTypeNoEffect duration type.
immunityTagsNoTags that block this effect.
stackingTypeNoStacking type for effect.
taskSettingsNoTask-specific settings.
attributeNameNoName of the attribute.
attributeTypeNoPredefined attribute type or Custom.
blueprintPathNoBlueprint asset path.
costAttributeNoAttribute used for cost (e.g., Mana).
costMagnitudeNoCost magnitude.
targetingModeNoTargeting mode for ability.
costEffectPathNoPath to cost Gameplay Effect.
setByCallerTagNoTag for SetByCaller magnitude.
cameraShakePathNoPath to camera shake asset.
replicationModeNoASC replication mode.
sourceAttributeNoSource attribute for attribute-based calculation.
stackLimitCountNoMaximum stack count.
targetAttributeNoTarget attribute for modifier.
activationPolicyNoWhen the ability activates.
attributeSetPathNoPath to Attribute Set asset.
calculationClassNoUGameplayEffectExecutionCalculation class path.
cooldownDurationNoCooldown duration in seconds.
instancingPolicyNoHow the ability is instanced.
modifierMagnitudeNoMagnitude of the modifier.
modifierOperationNoModifier operation on attribute.
cooldownEffectPathNoPath to cooldown Gameplay Effect.
particleSystemPathNoPath to particle system.
activationBlockedTagsNoTags that block activation of this ability.
blockAbilitiesWithTagNoTags of abilities blocked while this is active.
stackExpirationPolicyNoWhat happens when stack expires.
activationRequiredTagsNoTags required to activate this ability.
cancelAbilitiesWithTagNoTags of abilities to cancel when this activates.
stackPeriodResetPolicyNoWhen to reset stack period.
applicationRequiredTagsNoTags required to apply this effect.
magnitudeCalculationTypeNoHow magnitude is calculated.
preMultiplyAdditiveValueNoValue added before multiplication.
postMultiplyAdditiveValueNoValue added after multiplication.
stackDurationRefreshPolicyNoWhen to refresh stack duration.
Behavior2/5

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

Annotations provide readOnlyHint=false and destructiveHint=false, but the description adds little behavioral context. It does not disclose that the tool can modify existing assets (e.g., set_attribute_base_value), whether it saves changes, or any side effects. The 'create' wording is inconsistent with the broader manage/set actions implied by the schema.

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

Conciseness2/5

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

The description is a single sentence, which is concise, but it under-specifies a complex tool with 68 parameters and 27 action types. It is closer to an underspecified placeholder than a genuinely concise overview.

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

Completeness2/5

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

For a tool with 68 parameters, 27 enumerated actions, and no output schema, the description is far from complete. It fails to mention the range of operations (create, set, configure, get) or any constraints, leaving the agent to infer the tool's full capabilities from the schema alone.

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 parameters are already well-documented. The description adds no additional parameter meaning beyond the schema. Baseline 3 is appropriate since the description does not compensate or add value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the GAS resource domain (abilities, effects, attribute sets, cues) but uses the verb 'create' which is misleading because the tool's actions also include set, configure, add, and get info. It does not distinguish from sibling tools like manage_effect or manage_combat, which may overlap.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, no exclusions, and no context about the variety of operations it supports. The description simply states the resource type without any practical usage direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Flux-Point-Studios/unreal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server