Skip to main content
Glama

unreal_create_room

Create a simple room in Unreal Engine by generating scaled cube actors for walls and floor, with configurable width, height, length, and wall thickness.

Instructions

Create a simple room using scaled cube actors.

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

Input Schema

NameRequiredDescriptionDefault
widthNo
heightNo
lengthNo
paramsYes
name_prefixNoMCP_Room
wall_thicknessNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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. It reveals the construction method (scaled cubes) but says nothing about which level/context the actors land in, whether the operation is reversible, what permissions or editor state it needs, or how it behaves on name collisions.

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 single sentence is front-loaded and free of filler, which is good, but its brevity here reflects under-specification rather than tight authoring. Nothing is wasted, but far too little is said for a six-parameter construction tool.

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 described, but for a mutation tool with no annotations and 0% parameter coverage the definition leaves critical gaps. An agent cannot determine units, the meaning of the required params object, or the execution context from the description alone.

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% across six parameters, and the description adds no meaning for width, height, length, wall_thickness, name_prefix, or the required unspecified "params" object. Units are unstated (cm vs m), the required params blob is unexplained, and there is no indication of how dimensions interact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Create a simple room") and adds the implementation detail that it's built from scaled cube actors, so an agent knows what will exist afterwards. It does not differentiate from other creation siblings such as unreal_create_level or unreal_create_gameplay_prototype, which is why it stops short of 5.

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 statement of when this tool should be chosen over alternatives, nor any preconditions such as needing an open level or editor session. The agent must infer usage entirely from the name and one sentence.

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