Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

create_camera_rig_rail

Spawn an unrotated CameraRig_Rail actor in the Unreal Editor world, optionally at a chosen location with 2-100 spline points. Use the returned internal_name to position the rail later.

Instructions

Spawn an unrotated CameraRig_Rail actor in the editor world; with more than 2 points the rail is rebuilt as a straight 500-unit line along local X. Always labelled "CameraRigRail_MCP", so address it by the returned internal_name, e.g. in set_camera_rig_rail_position. Not saved.

Returns: { actor_name: string, internal_name: string, location: [number, number, number], num_spline_points: number, success: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoOptional [X, Y, Z] world location (defaults to origin; each axis within -100000 to 100000)
num_spline_pointsNoNumber of spline points on the rail (optional, default 2, valid 2-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / location / description
      Previous value: -"Optional [X, Y, Z] world location (defaults to origin)"New value: +"Optional [X, Y, Z] world location (defaults to origin; each axis within -100000 to 100000)"
  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?

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower, yet the description still adds rich behavior: the actor is unrotated, that >2 spline points triggers a rebuild into a straight 500-unit local-X line, a fixed 'CameraRigRail_MCP' label, and the fact it is not persisted. These are non-obvious operational traits an agent needs.

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 compact sentences plus a returns block; the core creation fact and the label/addressing caveat are front-loaded, and every clause carries signal (rotation, rebuild rule, label, persistence). No filler.

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?

Though there is no formal output schema, the description inlines the return shape (actor_name, internal_name, location, num_spline_points, success), so an agent knows how to consume the result. Combined with schema and annotations, nothing needed to call it correctly is missing.

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 coverage is 100%, so baseline would be 3, but the description adds meaning beyond the schema: the >2-point rebuild rule explains the observable effect of num_spline_points on rail geometry. The location parameter's effect is left to the schema.

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 specific verb and resource — spawning a CameraRig_Rail actor — and distinguishes itself from siblings by naming set_camera_rig_rail_position as the follow-up tool for addressing the rail. An agent can tell it apart from create_camera_rig_crane or create_camera_rig_asset without opening schemas.

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?

It says where the rail is created ('in the editor world') and that it is 'Not saved', which implies transient usage, and it references a sibling for subsequent positioning. However, it never states when to prefer this tool over alternatives like create_camera_rig_crane, or any exclusions or prerequisites. Usage is implied rather than explicit.

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