Skip to main content
Glama

unreal_set_collision_profile

Sets the collision profile name for a selected Unreal Engine object so its collision behavior uses the intended preset.

Instructions

Set collision profile name.

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_collision_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the verb "Set". It does not state whether the change is destructive or persistent, what happens to existing collision settings, what permissions or preconditions are needed, or whether the target must be selected first.

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 text is short and front-loaded, but its brevity stems from under-specification rather than compression of useful content. A single four-word sentence is not a structure that conveys purpose, usage, or parameter expectations.

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?

An output schema exists, so return values need not be explained, but everything else is missing: the target object, the mutation's effect, and the shape of the sole required parameter. For a tool whose only input is an opaque params object, this is far too little to invoke correctly.

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?

Schema description coverage is 0%: the single required parameter is an untyped "params" object whose contents are undocumented in both schema and description. The description does not say whether params carries the profile name as a string, a struct, or which additional fields it expects, so an agent cannot construct a valid call from this text.

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?

"Set collision profile name" names a verb and a resource, but the resource is vaguely defined: it does not say whether a collision profile name is applied to an actor, a component, or a mesh, nor which object is targeted. It is distinguishable from siblings like unreal_get_collision_info only by the verb, not by scope or effect.

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 offers no when-to-use, when-not-to-use, or alternative guidance. With siblings such as unreal_set_mesh_collision, unreal_generate_collision, and unreal_set_simulate_physics, an agent has no basis for choosing this tool over them from the definition 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