Skip to main content
Glama
Flux-Point-Studios

Unreal Engine MCP Server

manage_splines

Destructive

Create and modify spline actors, add or adjust points, attach meshes along splines, and query spline data in Unreal Engine.

Instructions

Create spline actors, add/modify points, attach meshes along splines, and query spline data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
saveNoSave the asset(s) after the operation.
scaleNoScale for spline actor.
widthNoWidth value.
actionYesSpline action to perform
endPosNoEnd position for spline mesh segment.
filterNoGeneral search filter.
pointsNoArray of spline points for batch creation.
endRollNoRoll angle at spline mesh end (radians).
spacingNoDistance between scattered meshes.
tangentNoUnified tangent (sets both arrive and leave).
endScaleNoX/Y scale at spline mesh end.
locationNoLocation for spline actor.
meshPathNoMesh asset path.
positionNoPosition for spline point.
rotationNoRotation for spline actor.
scaleMaxNoMaximum random scale multiplier.
scaleMinNoMinimum random scale multiplier.
startPosNoStart position for spline mesh segment.
actorNameNoName of the actor.
actorPathNoPath to actor.
endOffsetNoOffset from spline end for last mesh.
startRollNoRoll angle at spline mesh start (radians).
cableSlackNoSlack/sag amount for cable template.
endTangentNoEnd tangent for spline mesh segment.
pipeRadiusNoRadius for pipe template.
pointIndexNoIndex of spline point to modify.
pointScaleNoScale at spline point.
railHeightNoHeight of fence rails.
randomSeedNoSeed for randomization (for reproducible results).
splineNameNoName of spline component.
splineTypeNoType of spline interpolation.
startScaleNoX/Y scale at spline mesh start.
bClosedLoopNoWhether spline forms a closed loop.
forwardAxisNoForward axis for spline mesh deformation.
postSpacingNoSpacing between fence posts.
startOffsetNoOffset from spline start for first mesh.
leaveTangentNoLeave tangent for spline point (outgoing direction).
materialPathNoMaterial asset path.
startTangentNoStart tangent for spline mesh segment.
templateTypeNoType of spline template to create.
arriveTangentNoArrive tangent for spline point (incoming direction).
bUpdateSplineNoUpdate spline after modification (default: true).
blueprintPathNoBlueprint asset path.
componentNameNoName of the component.
pointRotationNoRotation at spline point.
segmentLengthNoLength of mesh segments for deformation.
bAlignToSplineNoAlign scattered meshes to spline direction.
bRandomizeScaleNoApply random scale to scattered meshes.
coordinateSpaceNoCoordinate space for position/tangent values (default: Local).
bRandomizeRotationNoApply random rotation to scattered meshes.
rotationRandomRangeNoRandom rotation range (degrees).
bSmoothInterpRollScaleNoUse smooth interpolation for roll/scale.
Behavior2/5

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

The annotations already indicate destructive behavior (destructiveHint=true) and non-read-only (readOnlyHint=false). The description adds no additional behavioral context such as persistence requirements (e.g., save parameter), irreversibility, or dependencies between actions, only restating high-level capability categories.

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 a single concise sentence with no redundant words, making it efficient. However, given the tool's complexity (21 actions, 52 parameters), the brevity borders on under-specification, but it still earns points for being tight and front-loaded with capability verbs.

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?

The tool is highly complex with 21 actions and 52 parameters, yet the description provides only a high-level summary. It doesn't explain the action dispatch pattern, template types, or how parameters map to actions. Without an output schema, this is insufficient for an agent to correctly invoke the tool without deep schema inspection.

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?

The input schema has 100% description coverage for all 52 parameters. The tool description does not add any parameter-specific details beyond the schema, such as how parameters relate to actions, but the schema already handles param semantics, so the baseline score of 3 is appropriate.

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

Purpose4/5

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

The description uses specific verbs (create, add/modify, attach, query) and clearly identifies the spline resource, distinguishing it from other manage_* tools. However, it doesn't enumerate the 21 actionable operations or explicitly differentiate the various capabilities, so it's clear but not fully distinctive.

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 about when to use this tool versus alternatives. The description simply lists operations without context on selecting a specific action, prerequisites, or trade-offs, making it purely descriptive with no 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