Skip to main content
Glama

unreal_set_linear_velocity

Sets the linear velocity of an Unreal Engine actor or component to control its movement speed and direction in a scene.

Instructions

Set linear velocity.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "unreal_set_linear_velocity"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It omits whether the operation is a mutation, what units the velocity uses, whether the target must have physics simulation enabled, and what happens if it is not.

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 sentence is short but this is under-specification, not conciseness; there is no mention of the tool's scope or of the parameter. A single line that conveys no usable information does not earn its place.

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

Completeness1/5

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

Output schema existence means return values need not be explained, but even so this definition is far too thin for a mutation tool. The one required parameter is completely opaque, and nothing about target selection, units, or physics preconditions is provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has a single 'params' property with no type, no nested properties and 0% description coverage, so the schema contributes nothing. The description does not explain what 'params' must contain, meaning the agent has no way to construct a valid call.

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

Purpose2/5

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

"Set linear velocity" restates the tool name almost verbatim and adds no scoping detail. It does not say which actor or component the velocity applies to, nor does it differentiate the tool from siblings such as unreal_set_angular_velocity or unreal_set_physics_enabled.

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?

The description provides no when-to-use guidance, no prerequisites (e.g. that physics simulation must be enabled), and no named alternatives. An agent must infer everything about applicability from the tool name alone.

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