Skip to main content
Glama

set_vehicle_wheel_setup

DestructiveIdempotent

Configure a vehicle wheel setup entry by index, specifying wheel class, bone, and offset. Resolves and loads the wheel class that generic property tools cannot reliably write.

Instructions

Configure ONE entry of a UChaosWheeledVehicleMovementComponent's WheelSetups array (wheel class, bone, offset) by index. USE THIS RATHER THAN the generic set_property_value / set_properties, which cannot reliably write the wheel class: it is a TSubclassOf nested in a struct nested in an array, and the generic path only FINDS an already-loaded class instead of loading it. This tool resolves the class explicitly and writes the whole struct element, growing the array to fit if wheel_index is past the end. READING them back needs no special tool -- the generic get_properties / get_property_value already resolves nested object refs correctly.

Returns: { actor_name: string, wheel_index: int, wheel_class: string, bone_name: string, additional_offset: {x,y,z}, num_wheels: int }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bone_nameNoSkeletal bone this wheel is attached to. Optional.
actor_nameYesEditor-world actor with a UChaosWheeledVehicleMovementComponent
wheel_classYesFull class path of the UChaosVehicleWheel subclass, e.g. "/Script/ChaosVehicles.ChaosVehicleWheel"
wheel_indexYesIndex into WheelSetups (>= 0). The array grows to fit if this is past the current end.
additional_offsetNo[x, y, z] additional offset applied to the wheel. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover safety (write, destructive, idempotent), but the description adds the crucial non-obvious behavior: the generic path only finds an already-loaded class instead of loading it, the tool resolves the class explicitly, writes the whole struct element, and grows the array if wheel_index is past the end. It also discloses the return shape.

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?

Front-loads the one-line purpose, then the sibling-routing guidance, then the read-path note, then the return shape. Efficient, though the return-type sentence is somewhat verbose.

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?

For a nested-struct array mutation tool with full schema coverage and rich annotations, the description covers purpose, alternative tools, the class-loading pitfall, array growth, and the read path. Only the explicit return shape is given without an output schema, and it is present.

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 coverage is 100%, so the schema already documents all five parameters including the class-path format and array-growth behavior for wheel_index. The description adds no syntax or format detail beyond the schema, so baseline 3 is correct.

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 (Configure) and a precise resource (one entry of a WheelSetups array) with the updateable fields named (wheel class, bone, offset) and a clear selector (by index).

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

Usage Guidelines5/5

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

Explicitly names the alternative tools (set_property_value / set_properties) and explains why this tool must be used instead, plus points to get_properties for the read path. This is exactly the when/when-not/alternatives guidance the dimension asks for.

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