Skip to main content
Glama

get_unreal_engine_path

Retrieve the current Unreal Engine installation path to configure development environments or resolve missing engine dependencies.

Instructions

Get the current Unreal Engine path

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_unreal_engine_path' tool. It checks if the enginePath variable is set and returns it as text content if available, otherwise throws an error. This is also the registration point using server.tool.
    server.tool("get_unreal_engine_path", "Get the current Unreal Engine path", async () => {
    	if (!enginePath) {
    		throw new Error("Unreal Engine path is not set")
    	}
    
    	return {
    		content: [
    			{
    				type: "text",
    				text: `Unreal Engine path: ${enginePath}`,
    			},
    		],
    	}
    })
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Get') but doesn't add any context about what 'current' means (e.g., cached, configured, or default path), potential errors, or return format. This is a significant gap for a tool with zero annotation coverage, as it leaves the agent guessing about operational details.

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?

The description is a single, clear sentence with zero waste—it directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple, parameterless tool and is front-loaded with the essential information.

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 simplicity (0 parameters, no output schema), the description is minimal but inadequate. It lacks context about what the 'current' path entails, how it's determined, or what the return value looks like (e.g., string path, error handling). With no annotations to fill these gaps, the description should provide more completeness for reliable agent use.

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 0 parameters, and the schema description coverage is 100%, so there's no need for parameter details in the description. The description correctly implies no inputs are required by not mentioning any, aligning with the schema. A baseline of 4 is appropriate since it doesn't need to compensate for missing parameter info.

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 tool's purpose with a specific verb ('Get') and resource ('current Unreal Engine path'), making it easy to understand what it does. However, it doesn't explicitly distinguish itself from its sibling 'get_unreal_project_path', which is similar in structure but targets a different resource (project vs. engine path).

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, context (e.g., when the path might be needed), or compare it to siblings like 'set_unreal_engine_path' or 'get_unreal_project_path', leaving the agent to infer usage based on the name alone.

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