Skip to main content
Glama

unreal_get_logs

Retrieve recent UnrealEngineMCP plugin logs to inspect editor errors, warnings, and execution history for troubleshooting.

Instructions

Get recent UnrealEngineMCP plugin logs.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and delivers almost nothing: it does not say whether this is a read-only snapshot, how far back 'recent' reaches, whether output is truncated or paginated, or whether a running editor is required. Only the vague adjective 'recent' hints at scoping.

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, and the purpose is front-loaded. However, brevity here reads as under-specification rather than economy, since critical invocation details are absent.

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?

A return-value schema exists, so outputs need not be explained, but the opaque required 'params' argument and the absence of any behavioral notes leave the definition short of what an agent needs to call it correctly. The gap is in inputs and behavior, not outputs.

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

Parameters1/5

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

The single parameter is an untyped, undescribed 'params' object with 0% schema description coverage, so the description must compensate and adds nothing. An agent cannot tell whether 'params' carries a log level filter, line count, time window, or is simply a placeholder.

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?

States a concrete verb ("Get") and resource ("recent UnrealEngineMCP plugin logs"), which is enough to distinguish it from the surrounding get_* actor/asset/blueprint tools without opening the schema. It stops short of explaining what "logs" covers, but the resource is clear.

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?

No guidance on when to call this versus other diagnostic tools (e.g., the compile-errors or automation-results siblings), no prerequisites, and no indication of what 'recent' means. The agent must infer usage entirely from the name.

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