Skip to main content
Glama
Sign In
UE5-MCP-Server

UE5-MCP-Server

by hahatu112113
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ue5_build_lighting

Build light maps and reflection captures for the level. This operation may take a long time and block the editor.

Instructions

Builds light maps and reflection captures for the level. NOTE: This may take a long time and block the editor.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ue5_build_lighting"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Without annotations, the description adds value by noting the long-running and blocking nature. However, it does not disclose whether the operation is destructive, requires specific permissions, or other behaviors that an agent should know.

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

Conciseness5/5

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

Extremely concise: one sentence providing the core purpose, plus a brief note. Every word serves a function, no redundancy.

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?

While the description is concise and covers the basic purpose and a warning, it lacks details on return values, error states, or prerequisites. Given the tool's complexity, more context would be beneficial for an agent.

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

Parameters4/5

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

The tool has zero parameters, so schema coverage is irrelevant. The description does not need to add parameter information; the baseline of 4 is appropriate as the description fulfills the role.

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

Purpose5/5

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

Description clearly states the function: building light maps and reflection captures for the level. This is specific and distinct from sibling tools which deal with functions, assets, actors, and other operations.

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 note warns about long execution time and blocking the editor, which provides important usage context. However, it does not specify when to avoid this tool or mention any alternatives, limiting guidance.

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