Skip to main content
Glama

unreal_generate_collision

Generate mesh collision for selected Unreal Engine actors to enable accurate physics interactions and hit detection.

Instructions

Generate mesh collision.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/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 behavioral burden, yet it discloses nothing: not whether existing collision is overwritten, whether the operation is destructive or reversible, what permissions or editor state are required, or what happens on failure. For a mutation tool with zero annotation coverage this is effectively a restatement of the name.

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 single sentence is short, but its brevity reflects under-specification rather than efficiency; there is no structure, no front-loaded scope, and nothing that earns it a place beyond the tool name.

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?

An output schema exists, so return values need not be explained, but the definition still omits the essentials for invocation: the meaning of the opaque params argument and any behavioral consequences of generating collision. For a write operation with no annotations and an undocumented nested argument, this is insufficient.

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 single required parameter "params" is an untyped object with 0% schema description coverage and no properties, and the description adds no information about what it should contain. The schema and the description together leave the caller with no way to construct a valid argument.

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?

The description names a specific verb and resource ("Generate mesh collision"), so the general operation is identifiable. However, it does not say what kind of collision is generated (simple/convex/complex), what the collision is generated from, or how it differs from the sibling unreal_set_mesh_collision, leaving scope ambiguous.

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 on when to use this tool versus alternatives such as unreal_set_mesh_collision or unreal_get_collision_info. The agent must infer that "generate" implies creating collision data from scratch rather than updating an existing setup, and no prerequisites or preconditions are stated.

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