Skip to main content
Glama

unreal_get_collision_info

Retrieve collision information for an Unreal Engine mesh to inspect collision settings and support debugging or editing.

Instructions

Get mesh collision info.

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

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
Behavior2/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 about whether the call is read-only, requires an open editor or a selected mesh, or errors when a mesh has no collision. The "get" verb weakly implies a safe read, but no real behavior is described.

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 sentence is short and front-loaded with the verb, but its brevity is under-specification rather than density; a few more words identifying the target mesh input and the returned collision data would cost little and add much.

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 shape need not be explained, but the input side is an opaque params object and there is no indication of context requirements for a tool that clearly needs a target mesh identifier. For a domain as structured as Unreal collision, this is inadequate.

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 is an untyped, undescribed "params" object at 0% schema coverage, and the description adds zero information about what must go in it. Since parameter count is above zero, the baseline-4 rule for parameterless tools does not apply.

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?

"Get mesh collision info" restates the tool name almost verbatim and never specifies what "collision info" contains (simple/complex collision geometry, shape types, per-body settings). It also fails to distinguish itself from close siblings such as unreal_get_collision_channels, unreal_set_mesh_collision, or unreal_get_mesh_info.

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

Usage Guidelines1/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, and no indication of how this differs from unreal_get_collision_channels, unreal_get_physics_info, or unreal_generate_collision. An agent must guess whether this reads existing collision or describes a set of channels/profiles.

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