Skip to main content
Glama
Sign In
unreal-mcp-additional-tools

unreal-mcp-additional-tools

by nodormu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_skeletal_mesh_lod

Configure the number of LODs for a skeletal mesh asset by providing its path and desired LOD count.

Instructions

Configure LOD settings on a skeletal mesh.

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": {
      "mesh_path": "<mesh_path>",
      "lod_count": "<lod_count>"
    },
    "name": "set_skeletal_mesh_lod"
  }
}

Input Schema

NameRequiredDescriptionDefault
lod_countYesNumber of LODs to generate
mesh_pathYesSkeletal mesh asset path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the burden of behavioral disclosure. It mentions 'Configure LOD settings' but doesn't disclose side effects like whether existing LODs are destroyed/overwritten, whether source art is regenerated, or if this is purely metadata configuration. The briefness leaves questions about undo-ability and performance impact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Efficient single sentence, minimal waste. Could be criticized for under-specification, but for the stated purpose it's appropriately sized. A slight improvement would be mentioning behavior or expectations.

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

Completeness3/5

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

For a tool with only 2 parameters and no output schema, the description is functional but thin. It doesn't explain the effect of 'configuring' LODs - does it regenerate them, adjust settings, or something else? The return value is unknown, but that's partially mitigated by no output schema. The sibling tools context (content management, source control, automation) suggests this is a UEFN/RPC automation, where concurrency considerations might be relevant but aren't mentioned.

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

Parameters3/5

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

Schema coverage is 100%, so the schema documents both parameters. The description references LOD settings generally but doesn't add meaning beyond the schema. The description 'Configure LOD settings' adds no parameter information beyond what schema already provides.

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 clearly states the verb 'Configure' and the resource 'LOD settings on a skeletal mesh'. It's specific enough to distinguish from sibling tools like apply_material or reimport_skeletal_mesh, though it could explicitly differentiate from other LOD-related tools (none currently exist among siblings).

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (configuring LOD settings) but doesn't explicitly state when to use this tool vs alternatives. It doesn't mention prerequisites like mesh path validity or LOD generation pipeline requirements.

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