Skip to main content
Glama

unreal_engine_mcp_version

Returns the MCP server version and non-secret configuration so AI clients can verify compatibility and review active settings.

Instructions

Return UnrealEngineMCP server version and non-secret configuration.

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": "unreal_engine_mcp_version"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/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. It does disclose one meaningful behavioral trait beyond the name: the returned configuration is 'non-secret', which reassures the agent that credentials are redacted. It does not state read-onlyness, whether a live connection is required, what configuration keys come back, or the response shape — notable gaps with no output schema and no annotations.

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?

A single front-loaded sentence with no filler; both clauses ('version' and 'non-secret configuration') carry distinct information. Nothing is repeated from structured fields and nothing is wasted.

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?

Complexity is low (zero parameters, no nesting), but with no annotations and no output schema the description is the only source of return-value information, and it stays at a high level — 'non-secret configuration' is not itemized. Adequate to call the tool correctly, but thin on what the result actually contains.

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 takes zero parameters, so the baseline is 4. The empty schema leaves nothing to misinterpret and the description introduces no phantom arguments that would mislead an agent into supplying input.

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?

Names a specific verb and resource: returns the UnrealEngineMCP *server* version plus non-secret configuration. The 'MCP server version' phrasing usefully separates it from sibling engine-level reads like unreal_get_version and unreal_get_engine_settings, though it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer this is a diagnostic/introspection call, appropriate before other operations to confirm server version or configuration. There is no explicit when-to-use statement, no exclusions, and no pointer to the engine-version sibling that a reader might otherwise confuse it with.

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