Skip to main content
Glama

unreal_get_project_info

Retrieves current Unreal Engine project information so AI clients can inspect project settings and context before editing or automating editor workflows.

Instructions

Get current Unreal project information.

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_get_project_info"
  }
}

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?

With no annotations supplied, the description carries the full disclosure burden and provides essentially none. 'Get' weakly implies a read, but the definition says nothing about whether the editor must be running, whether the call is expensive, or what scope of project data is returned; only the presence of an output schema saves the agent from total ignorance of results.

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

Conciseness3/5

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

One short sentence with no filler, but its brevity comes from under-specification rather than efficiency; there is nothing front-loaded because there is nothing substantive 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?

The tool is simple and has an output schema, so return values need not be described, but the definition still leaves the essential question unanswered: what project information, and under what conditions. For a zero-annotation tool whose only parameter is opaque, this is inadequate.

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

Parameters2/5

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

Schema description coverage is 0% and the single required parameter is an untyped, undocumented 'params' object. The description never mentions it, so the agent has no idea what to pass or whether it can be an empty object.

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

Purpose2/5

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

The description restates the tool name almost verbatim: "Get current Unreal project information" adds no specificity beyond unreal_get_project_info. It never says what 'project information' contains (name, path, engine version, plugin list?), so it cannot be distinguished from siblings like unreal_get_project_settings, unreal_get_project_modules, or unreal_get_project_diagnostics.

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 at all: no prerequisites (e.g. requires an open editor/project), no exclusions, and no pointer to any of the closely related project_* siblings. The agent must infer relevance from the tool name alone.

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