Skip to main content
Glama

get_recent_output_log

Fetch recent Unreal Engine Output Log entries to review warnings, errors, or diagnostic messages after tool execution. Use filter_category to narrow results.

Instructions

Retrieve recent lines from the Unreal Engine Output Log.

Use this after running any tool to check for warnings, errors, or diagnostic messages that Unreal wrote to the log.

Args: lines: Number of recent log lines to return (default 200, max 1000) filter_category: Only return lines containing this string (e.g. "LogBlueprint", "LogPython", "LogAssetTools", "Error")

Returns: JSON string: { "success": true, "lines": ["LogPython: Warning: ...", "LogBlueprint: Error: ..."], "count": 45, "filter": "Error" }

KB: see knowledge_base/12_MCP_TOOL_USAGE_GUIDE.md#overview Example: get_recent_output_log()

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesNo
filter_categoryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It documents the exact JSON return shape including success, lines, count, and filter, and specifies the default and max for lines, providing sufficient transparency for a read-only log retrieval tool.

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 well-structured with purpose, usage, args, return format, KB reference, and an example. Every section adds actionable detail without redundancy, and the core purpose is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with two optional parameters, the description covers when to use it, parameter semantics, return structure, an example invocation, and a knowledge base reference. Nothing needed for correct invocation is missing.

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

Parameters5/5

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

The input schema only lists parameter names, types, and defaults with no descriptions (0% schema coverage). The description fully compensates by defining 'lines' with default 200 and max 1000, and 'filter_category' with concrete example strings such as 'LogBlueprint' and 'Error'.

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

Purpose5/5

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

States the specific operation 'Retrieve recent lines from the Unreal Engine Output Log', naming the verb, resource, and scope. The usage note 'Use this after running any tool to check for warnings, errors, or diagnostic messages' further frames it as a general diagnostic reader, distinguishing it from other unrelated tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides usage context with 'Use this after running any tool to check for warnings, errors, or diagnostic messages'. It gives clear guidance on when to call the tool, though it does not name exclusions or compare with log-related alternatives such as pie_capture_log.

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