Skip to main content
Glama

unreal_set_mesh_lod

Configures mesh LOD settings to control level-of-detail behavior for meshes in Unreal Engine projects.

Instructions

Configure mesh LOD 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_lod"
  }
}

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 disclosure burden, and it delivers almost nothing: whether this mutates or replaces existing LOD configuration, whether it requires the mesh to be loaded or an asset path, and whether changes are undoable are all unstated. The only behavioral signal is the implicit mutation from "configure," which is a minimal contribution.

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?

The single sentence is short but under-specified rather than concise; it spends its only words restating the tool name and leaves the substance absent. There is nothing to trim, but also nothing informative to front-load.

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 no annotations and an opaque `params` blob, the definition omits everything an agent needs to call it correctly. Given the complexity of LOD configuration in Unreal, this description is not sufficient.

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 `params` object with no schema description (0% coverage), and the description says nothing about what that object must contain. This is the one parameter the agent must construct, and it is a complete black box in both schema and prose.

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?

"Configure mesh LOD settings" pairs a generic verb with the resource (mesh LOD), which at least separates it from siblings like unreal_set_mesh_collision or unreal_set_mesh_material. However, it never says what aspect of LOD is being configured (LOD count, screen-size thresholds, forced LOD, per-section overrides), so an agent still cannot tell precisely what the tool does.

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, no prerequisites, and no mention of related alternatives such as unreal_get_mesh_info for inspecting current LOD state. The agent must infer usage entirely 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