Skip to main content
Glama

unreal_get_collision_channels

Retrieves collision channel names from an Unreal Engine project, enabling AI clients to inspect and apply collision settings during actor, level, and Blueprint workflows.

Instructions

Get collision channel names.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/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 burden of behavioral disclosure, and it discloses almost nothing. It does not say whether this reads project settings, requires an editor session or loaded level, or what a 'channel' covers; only the existence of an output schema absolves it from describing return values.

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?

A single short sentence with no filler, which is front-loaded in intent, but the brevity comes from under-specification rather than economy. Nothing in it is wasted, yet nothing beyond the name is conveyed.

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?

Although an output schema exists and return values need not be explained, the tool has a required undocumented parameter and no annotations, so the description should at least establish the read-only nature and the scope of the returned channels. It does neither.

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

Parameters2/5

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

There is one required parameter ('params') with 0% schema description coverage, and the description says nothing about it. At minimum the description should indicate whether params is an empty placeholder or carries filtering/context data, so this leaves a real gap rather than merely deferring to the schema.

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?

The description 'Get collision channel names' essentially restates the tool name unreal_get_collision_channels, adding only the word 'names'. It gives no scope, no indication of what a collision channel is in context, and no differentiation from siblings such as unreal_get_collision_info or unreal_set_collision_profile.

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 when-to-use guidance at all: no statement of when to call this instead of unreal_get_collision_info, and no prerequisites or exclusions. The agent must infer usage purely from the tool name.

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