Skip to main content
Glama

unreal_set_mesh_collision

Set a mesh's collision profile and settings to control how Unreal Engine assets handle blocking, overlap, and physics interactions.

Instructions

Set mesh collision profile/settings.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it says nothing about whether this mutates persistent assets, what defaults or existing settings are overwritten, whether the mesh must be non-collision-primitive, or what authorization/asset-state is required. "Set" implies mutation but adds no risk or side-effect context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-liner is certainly brief and front-loaded, but it is under-specified rather than concise; the length reflects missing content, not disciplined editing.

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 for a mutation tool with an entirely opaque input object and no annotations, the description leaves the agent without enough to invoke it 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?

The single parameter is an untyped opaque object named "params" with 0% schema description coverage, and the description provides no indication of what fields it expects. This is the worst case: the agent literally cannot construct a valid call from the available information.

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 mesh collision profile/settings" gives a verb and resource but is vague about what exactly is being modified, and it overlaps with the sibling unreal_set_collision_profile without distinguishing the two. An agent cannot tell from the text whether this is the profile-setter or a broader settings mutator.

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?

No when-to-use, when-not-to-use, or alternative routing is provided, despite an obviously competing sibling (unreal_set_collision_profile) and an adjacent generate step (unreal_generate_collision). The agent must guess which tool to pick.

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