Skip to main content
Glama

set_unreal_engine_path

Configure the Unreal Engine installation path for the unreal-mcp server to enable proper integration and functionality.

Instructions

Set the Unreal Engine path

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Implementation Reference

  • The handler function sets the global enginePath variable to the user-provided path and returns a confirmation message in the MCP content format.
    async ({ path }) => {
    	enginePath = path
    
    	return {
    		content: [
    			{
    				type: "text",
    				text: `Unreal Engine path set to ${path}`,
    			},
    		],
    	}
    },
  • Zod schema defining the input parameters: a single 'path' string.
    {
    	path: z.string(),
    },
  • server/index.ts:74-92 (registration)
    Registration of the 'set_unreal_engine_path' tool on the MCP server, including name, description, schema, and inline handler function.
    server.tool(
    	"set_unreal_engine_path",
    	"Set the Unreal Engine path",
    	{
    		path: z.string(),
    	},
    	async ({ path }) => {
    		enginePath = path
    
    		return {
    			content: [
    				{
    					type: "text",
    					text: `Unreal Engine path set to ${path}`,
    				},
    			],
    		}
    	},
    )
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Set' implies a mutation, but the description doesn't specify whether this changes global settings, requires admin permissions, is persistent, or has side effects (e.g., affecting other tools). It lacks details on error handling, validation, or what happens if the path is invalid. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

The description is a single, efficient sentence with no wasted words, making it easy to parse. However, it's overly concise to the point of under-specification, as it omits necessary details for a mutation tool. While structurally sound, it could benefit from additional context without losing conciseness.

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?

Given the tool's complexity (a mutation with no annotations, 1 undocumented parameter, and no output schema), the description is incomplete. It doesn't explain what the tool returns, how changes propagate, or error conditions. For a configuration-setting tool in a development environment, more context is needed to ensure safe and correct usage.

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?

The input schema has 1 parameter ('path') with 0% description coverage, so the schema provides no semantic context. The description adds minimal meaning by implying the parameter is a path for Unreal Engine, but doesn't elaborate on format (e.g., file system path, URI), constraints, or examples. With low schema coverage, the description partially compensates but remains vague, aligning with the baseline for moderate value addition.

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?

The description 'Set the Unreal Engine path' clearly states the verb ('Set') and resource ('Unreal Engine path'), making the purpose understandable. However, it lacks specificity about what this path represents (e.g., installation directory, project engine association) and doesn't distinguish it from its sibling 'set_unreal_project_path', which is a similar configuration tool.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an Unreal Engine installation), exclusions, or compare it to sibling tools like 'get_unreal_engine_path' (for retrieval) or 'set_unreal_project_path' (for project-specific paths). Usage is implied but not explicitly defined.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/runreal/unreal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server