Skip to main content
Glama

unreal_get_mesh_bounds

Retrieves a mesh's bounding box and dimensions in Unreal Engine, helping you position, scale, and align assets accurately.

Instructions

Get mesh bounds.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/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 and discloses nothing: not whether it is read-only, whether bounds are local or world space, whether it works for skeletal meshes, or what happens with an invalid path. For a look-up tool with zero annotation coverage this is a substantive gap.

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?

It is a single short sentence with no waste, but this is under-specification rather than concision. There is no front-loaded scope statement because there is effectively no content to front-load.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The existence of an output schema relieves the description of explaining return values, but nothing else is covered. An agent calling a parameterized mesh-inspection tool needs to know what the opaque 'params' object expects, and the description provides no help at all.

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?

There is one required parameter, 'params', whose schema is an untyped object with 0% description coverage, and the description says nothing about what to put in it. With a parameter count of 1 the 0-param baseline of 4 does not apply, and nothing compensates for the coverage gap.

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 bounds" restates the tool name almost verbatim and adds no scope beyond it. It does not say which mesh (asset path vs. selected/active mesh), which coordinate space, or how it differs from adjacent siblings such as unreal_get_mesh_info or unreal_get_mesh_sections.

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?

No when-to-use guidance, no prerequisites, and no mention of any alternative tool. An agent has no basis in the description for preferring this over unreal_get_mesh_info when inspecting a mesh.

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